Re: More weather problems...should be easy
Brian Wolven <[email protected]>
| Newsgroups | gmane.comp.windows.shells.litestep |
|---|---|
| Message-ID | <[email protected]> |
Hale, Paul wrote:
> I am having a problem after I update my weather. For some reason, when I
> create the labels for the current condition or the forecast, lsColor
> doesn't seem to register. IE, none of the color evars are recognized.
>
> OK, so here is the original: (forgive wrapping)
>
> *Alias !getWeather !execute [wscript $Weatherscript$ %1 /prefix:loc1
> /bang:!UpdateWeather]
> *Alias !UpdateWeather !Execute [!reload][!NetReloadModule
> lscolor-1.6.1][!popuprescan][!LabelRefresh dateTime][!LabelRefresh
> WeatherButton][!netReloadModule $timerModule$]
>
> Here is mine:
>
> *Script bang !getWeather
> *Script exec !Execute [wscript $WeatherDir$WeatherNotDLL.vbs]
> *Script exec !reload
> *Script exec !NetReloadModule $ColorModule$
> *Script exec !PopupRescan
> *Script exec !LabelRefresh Forecast
> *Script exec !LabelRefresh CurrCond
> *Script exec !netReloadModule $TimerModule$
> *Script ~bang
>
> Whats the difference of the two? Besides the label names of course.
Hrmmm, the docs say:
!PopupRescan ["reload"]
This Bang completely Resets xPopup and Reloads ALL settings.
If you specify the optional "reload" then it reloads all settings from the rc-files.
Attention:
"!PopupRescan reload" calls a !Reload, and therefore a loss of manually set
evars happens.
A plain "!PopupRescan" is not causing the loss of evars from memory.
So if you're not doing a "!PopupRescan reload" then it's likely just a timing issue.
---------------------------------------------------------------------
Can't Unsubscribe? Check http://desktopian.org/listunsub.html
LS List Homepage: http://wuzzle.org/list/litestep.php
Get the LS FAQ: http://lsfaq.shellfront.org