Interesting accweathercore1 bug?

[Scar]

Any time I'm using the accweathercore1 core, it doesn't remember my default or desired location information if the pc is powered off and back on. It always reverts back to some location in another state no where near my current location. Any ideas whats causing it to change, or how to fix it? Doesn't seem to matter what widget I use, if the accweathercore1 is used to gather weather info, they all have the same problem.

[Jackalope_908]

That sounds weird. Have you removed ALL other locations so yours is the only one it can choose from? Another option to try is, is yours the first in the queue, with the assumption that if it's going to default, it'll go to the top of the list?

[Scar]

I have two locations in the list, my city, and a city next closest. It never picks either of them, it by default chooses "Chantilly Virginia" which is 418 miles away from me. I'm in South Carolina. Chantilly isn't even a choice I've ever set up. The problem is, there isn't a lot of documentation that I can find for the cores, how they work, or how they decide on location. And Xwidget seems to be lacking any documentation as well. Assuming it looks at my IP address, it should show my IP in the Atlanta Georgia area (because I use a VPN service).

When I look at the “settings” file located in my Xwidget/AppData folder when I correct the weather info, it states:

[Root]
isFirstRun=0
ThemeName=Strings
EnabledDateTimeAlwaysUsesSysLang=1
AutoStart=1

[accuweather]
citycode=335462
cityName=Conway
fullCityName=United States,South Carolina,Conway
interval=900000
isMetric=0
enabledProxyServer=0
lang=en
displayCityName=Conway

Which is correct. However, as soon as I reboot my pc, or restart the widget, it changes the file to read:

[Root]
isFirstRun=0
ThemeName=Strings
EnabledDateTimeAlwaysUsesSysLang=1
AutoStart=1

[accuweather]
cityCode=336309
cityName=Chantilly
fullCityName=United States,Virginia,Chantilly
interval=900000
isMetric=0
lang=en
displayCityName=Chantilly

No idea how/where its picking that up. Something, somewhere, its overwriting the file after each reboot, power on, or restarting of the widget. If the core is trying to identify my location by some location service, I would hope there are options to disable it, forcing a manual choice, but I have no clue where that switch would be (assuming thats even the problem).

Any ideas?


********** Update ***********

Ok, I have proven out that it is using some automated "location service", for when I turn off my VPN and connect to my ISP localy, it uses that location. So the new question becomes, how do you disable the "Location Service" within the core, and force it to choose a manual choice?

[XDesktopSoft]

Hi, you just need set a default location to disable the auto location: right-click the weather widget and select menuitem "Change location" and input your city name to search and select.

[Scar]

I've done that. I don't actualy have a "Change location" option, I have "Update Weather" "Weather information" and "Metric Imperial Units". If I choose weather information, I can change it to my local choice. But once I reboot my pc, or restart the widget, it defaults back to Chantilly Virginia. The only way to make it choose my city, is to manualy choose it every time I log on to my pc. Its not automaticly storing or remembering my options.

Ok, I've looked at the "menu" option within the widget, its set to the accweather core as "!ShowSetting" which seems to be how the other weather apps claim the option to change the location. Brings up the dialog to search for locations, which as before, allows me to change the location, but doesn't hold it when the widget is restarted, or the pc is restarted. Still going back to Virginia. :-)

[Dajonaga]

I happen to have the same issue... Changing Windows 10 location seems to work breifly... then it started to pick a new location... not the first one, or my choosen one... but a third one... still looking how to fix it.

[Scar]

Originally posted by Dajonaga:

I happen to have the same issue... Changing Windows 10 location seems to work breifly... then it started to pick a new location... nor the first one, or my choosen one... but a third one... still looking how to fix it.

Hi Dajonaga,

Yeah, there are a couple of bugs with the core. One of them is the manual setting and disabling of the automatic location set doesn't work. If you want something other than the automatic city choice, you have to manually set it each time the widget starts.

The other bug is the Wind Speed variable is invalid and not reading a proper value. The “curWindSpeedWithUnit” and/or “curWindSpeed” doesn't report. There are two values both these report, 0 or 8.

So, lots of bugs. And I'm still in search for answers.