Windguru for Windows Mobile 6.5
Most of you visiting this site are probably here because of the Windows Mobile 6.5 application for the world famous Windguru!
Thanks for all the messages of support I receive from the many, many people using the application. I'm really pleased you are able to use it and I trust it helps you get some great windsurfing / kitesurfing / sailing / other wind sport.
Please note that due to the high number of comments/questions that I receive it is not possible to reply individually. Please have a read through the FAQ below before contacting me.
13 February 2011:
Bug identified with mapping where users have regional settings which use a comma (,) as a decimal separator -this will mainly impact users in Continental Europe.
The workaround is to change your settings to US or GB English.
I hope to have fix out soon.
8 February 2011:
Version 1.3 has been released after receiving some good feedback from a number of users.
1. Improved memory management, some users were reporting an 'OutOfMemory' exception on occassions.
2. Greatly improved caching and control over what is cached and for how long - users were asking that they could keep a forecast cached for a number of days if out sailing and out of mobile range.
3. Menu simplification - streamlining a couple of menu items and cleaning up the code.
4. Custom spots available in 'Favourites'
5. Some minor bug fixes.
15 December 2010:
Version 1.2 has just been released and has the following features/fixes
1. Improved forecast rendering which uses far less phone processor time
2. Faster scrolling through the forecast
3. Forecast can now be scrolled left to right to see more days
4. Support for either Google or Openstreet maps
FAQ:
Multiple Days of Forecasts:
As of version 1.2 you can now scroll left to right to see more days of forecast.
Maps:
The 'Spot' maps in the application are downloaded externally from the Internet using either Google or Openstreet maps. If the maps don't load or they take a long time then it is because of your internet connection.
You should get two different maps which are overlayed on each other. The first map is a close-up of the location. You can get a zoomed out map by scrolling left or right on the first map image.
Maps - 'The remote server returned an error: (403) forbidden':
Some users report a 'The remote server returned an error: (403) forbidden' when trying to view a map. This issue is intermittent and appears to be an issue with the mapping server delivering the mapping image. I'm unsure how to resolve this problem.
Horizontal Scrolling:
The horizontal scrolling is not as smooth as the vertical scrolling. I'm aware of this situation and it is primarily because the framework I've used to support the scrolling is implemented this way. At this stage I don't intend to change the implementation as it still works fine.
Latest .NET Compact Framework:
You may receive a message saying you need a newer version of the .NET Compact Framework. If this is the case then you need to get a copy of the NETCFv35.wm.armv4i.cab installation file. This can be done by following any of the following 3 methods:
Search for NETCFv35.wm.armv4i.cab in your favourite search engine and find a link to installation instructions.
We are unable to provide a link to the download directly as we are not licensed to distribute the software.
Error: Unable to read data from transport connection:
You may get an "Unable to read data from the transport connection. Unknown error (0x0)" error even when your data connection is active and strong.
There is a lot of discussion on the web about this error however I'm unsure what the solution is.
Some say that it appears to be a problem with the Microsoft Compact Framework dropping packets when connecting to the type of web server that Windguru uses. This issue is under investigation. If you encounter the error, you can usually just attempt the action again and it will typically be successful.
There is a suggested fix at this page however changing the settings on my phone has not resolve the issue.
CPU Usage:
Some of you have reported high CPU usage. This has improved dramatically with version 1.2 due to a better rendering implementation and does not appear to cause an issue with any of the more recent phones (2009+).
High Memory Usage:
The forecast is a fairly detailed piece of graphics so it is rendered and then persisted as an image in memory. The more forecast information the larger the memory footprint. I'm not aware of this being an issue on any of the more recent phones (2009+)