My prior post works if Weather Watcher is installed in it’s default location and it can be tweaked to handle a similar install on a different drive even. It does not work if one installs it on a multi-user system with individual profiles. There is no way to separate the folders between the drive and “Weather Watcher”. And if someone goes crazy and renames the Weather Watcher folder something like WW567… well we don’t even want to go there. :lol:
var EdsAPath = escape('[INSTALL DIRECTORY]');
alert(EdsPath);doesn’t even help.
Ohh, yeah, I don’t know what the heck I was thinking - I guess I didn’t read your code at all…
By loading the path into an input field [preferably of the ‘hidden’ type] there should be no problem using it all over…
You’d need to add this somewhere in the beginning of the WTP:
And then add this [or access the field in a similar way each time you’d wanna use it]:
var thePathToTheDirectoryWhereThisInstanceOfWeatherWatcherWasInstalled = document.getElementById("textFieldContainingTheWeatherWatcherInstallPath").value);
I know it’s not the pretty way, and that it must be possible to do it nicer… But it should do the trick…
Hope it helps more than confuses…
And hey, I really have a skill for naming variables [:D]
That’s a pretty clever solution Fl?gger! I’ll have to give it a try. But we shouldn’t have to be playing tricks with the TAGs, they should be in formats acceptable to be worked in HTML and Jscipt code. And it’s probably more efficient being done in VB than Jscipt so I would still like to see the TAG’s options expanded to support our needs. :icon_smile:
Hehe, thanx, just figured that in order to access a string with single backslashes, you would have to do it from outside any scripting language that would interpret them. And magically it worked :mrgreen:
But I do agree, it should be available in an escaped version, otherwise it’ll be to much a hassle to use… Maybe the two could co-exist, like so many other things…?
I’m thinking something along the lines of having an [INSTALL DIRECTORY] and an [INSTALL DIRECTORY ESC]…
And while we’re at it, why not have tags for the last of the skins? I’d like info on atleast the interface too…
Originally posted by Fl?gger
And while we’re at it, why not have tags for the last of the skins? I’d like info on at least the interface too… 2b || !2b
I agree. I had asked for tags to indicate the interfaces’ name and WW’s install folder so I could access the interface’s icons but it appears Mike misunderstood. The new [SKIN FORECASTS] tag has the name of the forecast skin, we need a [SKIN INTERFACE] tag.
So for 5.6.8 we would like to have tags for;
[SKIN INTERFACE] - name of the interface being used.
[INSTALL LOCATION 2] - the WW install folder with 2 ""s.
[INSTALL LOCATION X] - the WW install folder with “/” in place of “”.
[ALERTS SOUND] - the complete path and filename of the New Severe Weather Alert .wav file. :razz:
Well, I finally got to try this concept. A couple of your parms threw me for awhile but once I got around them I got this to work:
EdsMoon=“file:///” + EdsMoon.replace(/\/g, ‘/’) + “/Skins/Forecasts/Eds Stone Soup/”;
The Input Type ID parm might have caused my problems with the getElementById method not working for me but I didn’t catch on to it till after I changed the document line completely around.
Anyways, this approach may work better for people with older systems.
In order to please all, I’d say the proper code might/should be as follows
This way, if it doesn’t find it one way it’ll try the other, thereby working for even more users…
As for your systems drag, I wouldn’t think it should have to much to do with the JS… Would seem odd… But, if it does, you might want to consider recoding some of your JS code or maybe design functions with broader uses, instead of just coding everything where you need it :razz:
And btw, thank you for doing all the coding these days - now there’s another feature for me to copy that is, if it’s okay with you - I wouldn’t wanna offend anyone…
Well, I did copy the technique from some code I did awhile ago. But, it works in IE which is the environment of WW, it should work on older systems running IE 5.x, and it works in Netscape. If it doesn’t work in IE 7 then I have a problem but until then… :icon_smile:
And now that I have it working I can play with changing it to official W3C standards. But when I was struggling with it, function trumped standards.
I understand. But we have different design objectives. I try to keep my changes modular so they can be reapplied or overlaid to newer versions of Mike’s template conveniently. If I was designing my own, independent, version of a skin I would code for efficiency.
You’re most welcome but you’re the one doing all the coding. The new options to resize the WW window are extensive. As for copying I like seeing my name/id in print so, as long as you keep including
"-The option of choosing EdP’s ‘real’ pictures of the moon " :shock:
in your list of acknowledgements I’m flattered and happy. :lol: :icon_smile:
And as an aside:
Mike when quoting prior text the icons end up as simply proper names. Can that be fixed? I suspect it’s due to the icon’s title being used in the quotes rather than the icon’s shortcut. For example the word Wink rather than semicolon dash parrens or even icon_wink.gif.