Current WeatherGALE Issues

---

1.1.15

1. If the Main Window is displayed and you try to switch to another task, you'll be unable to switch back to the WeatherGALE Main Window as expected. A fix for this issue will be released ASAP. Meanwhile, a special notice of this problem has been posted visibly on the Support page.
2. One user has reported an issue which I believe to be caused by the Microsoft debugger, part of the dot net (.net) development environment. When a locations update is occurring, a debug dialog with a Yes/No question appears; if the user selects Yes to debug, the machine locks up; if the user selects No to debug, the software apparently continues without problems. At one time, I had Microsoft Visual Basic dot net Standard installed for evaluation purposes of accessibility, and I recall a number of other softwares raising the Microsoft debugger in a manner similar to what this user describes. I'm therefore going forward on the assumption that this is what's affecting WeatherGALE. I'll release a new version with a fix as soon as I feel I've eliminated the problem, but such a fix is likely several months out; I'd expect to have a fix released no later than mid 2006, but continue to watch this space for more information as it becomes available.
3. The cooling fan issue mentioned in the 1.1.8 notes (see below) remains a pending fix. I'm working on it folks - hopefully by the next release. Until then, consult the temporary fix given in the original 1.1.8 note.
4. Also a pending fix are some blank city entries which somehow managed to make their way into the locations database files used by WeatherGALE. Unfortunately these entries throw off the true city count, which is actually somewhere around 12,985, not 13,012 as reported in the software.
5. Yet another pending fix that's also related to the locations database files is a method of providing some cities that aren't included in the database because they don't conform to the same layout used by the bulk of cities in the data providers' system. I'll get these cities into the database someday when time permits.
6. I've been concerned for some time about the lack of control I have over the data connections themselves. This lack of control has everything to do with the pending cooling fan issue and the sluggish performance of the Cancel button when WeatherGALE is performing a locations update. I'm trying to work on some alternatives for this as time permits; however, unless something seriously affects your internet connectivity or unless the data provider creates significant changes in their web site pages, WeatherGALE generally performs well despite the current data connectivity issues.

1.1.14

1. A known issue appeared early on December 8, 2005 that affected data connectivity and processing. This bug was caused by the data provider making some changes in their site pages; this in turn fouled the WeatherGALE data parser and this, combined with the lack of data connectivity control inherent in the current software, mushroomed into the December 8 issue. This sort of bug is to be expected so long as WeatherGALE is free software, because in order to keep it free I must parse the weather data off web pages; this works fine if the data provider keeps their site pages fairly consistent, but some changes cannot be forseen or dealt with until they occur - this is what happened on December 8.

1.1.8

1. The WeatherGALE task appears in the Windows Task list when WeatherGALE resides in the system tray. This is to provide the user with as much control as possible over the task. If the task were not visible in the Windows Task list, the user would have much less control over the task during system instability - the user would never be able to force the task to end if circumstances required this action. Currently no action occurs if you switch to the WeatherGALE task while it resides in the system tray, and this action will likely remain this way. This functionality is a matter of choice, and is a design/function decision that must be made in order to create the best possible options for the majority of users.
2. Another issue concerning the cooling fan running on systems that monitor processor temperature/activity is known to occur on an intermittent basis when WeatherGALE is trying to update locations and is experiencing a significant amount of errors or problems. The temporary fix for this is to show the Main Window and select the [Cancel] button. This should stop the locations update in progress and cause the cooling fan to resume its normal state. I'm working on this problem folks, just give me some time to try to make sure I've got it ironed out.
3. If WeatherGALE connectivity is disabled and the [OK] button is selected in the Locations Manager, your Locations list changes will be saved but a runtime error 5 will occur. The current workaround is to always make sure WeatherGALE connectivity is enabled if you're planning to make any changes to your Locations list in the Locations Manager. This bug will be corrected in the next release so the runtime error 5 will not occur.
4. In the city list for Missouri, United States, the first city in the list appears to be blank. Thought I had squashed all those little blank buggers - hopefully by the next release.
5. There is a known issue with the Locations Manager window not fitting a minimum 800 by 600 resolution display which will be resolved in the next release. Please be patient folks, this one slipped by last minute.

1.1.0

1. The title bar caption of the Locations Manager currently reads "Locations", but should read "Locations Manager".
2. If your system monitors processor temperature, you may notice the cooling fan starts after the Locations Manager has been displayed for a period, but stops as soon as you close the Locations Manager. This is due to some old code that will be retired in the next release, which should resolve the problem.
3. The locations database contains some entries labelled "Name Unknown". These entries were discovered after the software was posted for release.
4. An error 401 occurs when no locations file exists and the software tries to show the Locations Manager. My apologies to all new users who downloaded the 1.1.0 release and were unable to use the software - a fix is in the works and should be released no later than October 26, 2005. Anyone who received this error and is reading this - please give the software another chance!
   
   

Copyright (c) 2002-2008, Thinkzo Systems. This web page is part of the Thinkzo Systems web site and should not be linked to from any other web site. Unless otherwise noted, the contents are property of Thinkzo Systems and may not be reproduced without permission.