Thanks for the answer. I will wait for the version with the animated weater and moon without the radar.

By the way: I had that empty extended view once too (after wildly clicking on the object, I have to admit).

Mannlister, when it's in the state you picture, what happens when you doubleclick on the sun, clouds, or temp as I suggested? Also, regarding making it a shortcut to your browser: it's an object. Right-click on the part you want to modify and select properties, then change the type of object to shortcut and make it a shortcut to anything you want. I won't be doing those types of mods I made it an object instead of a widget so people can do that for themselves. (See the DX docs on configuring objects) But if you break it, you've bought it!

Will: when i doubleclick the sun or temp it opens the radar and closes it. the transparent part that you see in the screenshot stays there.

also, thanx for the tip on adding a link to an object. i've never done that before but now that you mention it i remember seeing it and it makes perfect sense. thanx!

Mannlister: then something is corrupted. Doubleclicking the sun/temp will only show/hide the radar if the forecast is in it's expanded "Big" state, and it will only register the "Big" state after making all the forecast objects visible. It will only show the big-temp when it is in the small state, not the big state. Programatically, it cannot enter a state when it can toggle the visibility of the radar at the same time the big-temp display is visible. I looked at the code, and cannot envision any series of normal user clicks that could cause it to become in a half-collapsed/half-expanded state. Also, it hides the big temp before entering the "Big" state. If I were you, I'd delete the dxpack for the object, and your theme, and all files in the theme directory when DX is shut down. Then download the object fresh. If a bug exists, it is not only so subtle that I cannot detect it, but it has also never manifested itself for me.

Hello,

The work you have done here is plain incredible. Functional and awesome looking...you can't ask for much more. Thank you.

Still only at a 9???

(can't believe his eyes)

Roger, thanks very much! I'm glad you like it.

I'd love to know what people's favorite feature is. I know a lot of people are partial to the customizable background (or "skinning" feature) but for me it's the animation and the moon.

One Word.. WOW. Exactly what I wanted someone to create. Excellent work!!!!!

I just heard from Stardock about a solution to performance problems with LookingGlass.

You should use Regedit and set HKEY_CURRENT_USER\Software\Stardock\DesktopX\DynBitmapCaching=1

This turns on Dynamic Bitmap Caching. On the machines I have tested this on that had "memory allocation issues" with LookingGlass before, setting this value to 1 reduced DX memory usage by 60-85%. It makes a HUGE difference. One machine went from allocating 317MB to 46MB. If you are not having any such problems, it is probably because this is already set properly in your version of DX. I am told it will be turned on by default in the next release.

Hi Will,

Love the wx suite. I have a problem, though. When I first import it, it arrives on my DX desktop with a z-order of "Desktop". If I change the z-order to "Normal" so that I can use the F9/F10 overlay keys, then I lose the ability to change the target city zip code. After a z-order change, I can't highlight the city in the frame, and changing the zip in the script has no effect. To restore functionality, I have to delete the suite and re-import. But then I'm stuck with "Desktop" z-order again. Any ideas?

Thanks,

Jeff

PS - I give this a 10 for animation, ease of background changing and overall usefulness. Best weather object I've seen yet.

An additional note:

The loss of function occurs if I change any of the "color" properties of the frame (parent) as well.

What I also see is ?mixup? in transparency or internal z-order...it seems that after the properties sheet is modified that the whole display inside the frame has acquired a "foggy" look to it, as if it is underneath something. When I first import the object, everything inside the frame is crisp and clear.

Maybe these two issues are related - I can't see the interior objects well and I can't access the hot spots to change temp display or location because they are all put underneath some element when the properties sheet is changed.

Jeff

Sorry to keep bugging you, but Mannlister's issues arise for me after saving a DX theme or rebooting the computer (without saving the theme first). Adding to the mystery are 3 script errors that appear after I save a theme with the LGWS in it. One is a type mismatch for the windowframe image and the other two occur on opening/closing the satellite radar image - they complain about "object required". Code line references in the script are given, but no code text is part of the error message.

The z-order of your objects change on their own when the properties of any of the objects are modified. Going into the object list and restoring the original z-order solves the 2 issues that I posted about earlier.

I'm going to see if the latest build of DX (2.21.029) dated today fixes any of these issues. Following your earlier advice, I will completely uninstall DX and then install the new version.

Jeff

Jeff: No problem at all. Let me try to shed some light on the issues.

1.It has been true for a long time that saving a DX theme with very complicated objects will sometimes mangle execution of whatever is currently running. Usually the theme is saved correctly, and if you just delete everything and then load the newly saved theme, all will normally be well. This is a DX issue, and you can experience it with many objects, not just LG.

2. The Z-order of my objects does not "change on their own". Z-Order management is solely the responsibility of DX. The code for the object NEVER, EVER modifies Z-order. If you want to change the Z-order, you'll need to change it for all the objects, and then use "Z-up/down" to get them in the right Z-order (study it first). DX doesn't really do a good job of changing the overall Z order of a compound object. You can't click on the zip because you have something in front of it after messing with the Z-order, probably "FrameGlass". It's the "FrameGlass" object that is that "foggy look" you describe. Pay attention to the image files of what you're modifying, and keep frameglass in the back.

3. For whatever reason, when running a large complicated compound object with multiple parent/child relationships (like LG) DX seems to have fits when you modify any properties of any of the members. This is a DX issue. If you want to do a whole boatload of modifications, I would suggest stopping all the scripts first, then re-enabling them when done. That seems to make DX happier.

4. Let me reiterate: LGW (the code) does not know or care what (for example) the color or font of the "big_tmp" object is. However, if you modify the color, there's a big pause, DX resets the object, and magically changes the Z-order of "FrameGlass". This has zero to do with LWG, and is something going on with DX (in all versions).

5. Those "object required" messages are because DX re-initialized an script (like weather_cc) that referred to another ScriptObject, before initializing the object it referred to (WeatherFrame). The easiest way is don't immediately dismiss the error- wait for LG to initialize and show the current conditions, then just click continue.

6. Regarding Mannlister's issue with the Frameglass showing while the object is in compact mode and it becoming unresponsive, I've confirmed that this is a bug (essentially in DX) whereby DX in certain circumstances (having largely to to with load on the explorer.exe process) re-activates a state transition without invoking OnStateChange or OnStateChanged in the object. The original cause is a DX bug, but it provokes a bug in LWG. This is like the situation where the code is provably correct, but there's a compiler bug. Bottom line is the program doesn't do what you want... This problem is impossible to completely eradicate progamatically with current DXScript limitations, but I will be releasing a new version in a few days that makes it "almost" impossible to occur, as well as adding some new functionality.

Finally let me say this: LookingGlass is the most complicated weather object ever made for DX, and it is a lot more sophisticated in its construction than any other weather object you've worked with. If anyone is going to modify it for their own use, and still wants it to work correctly, they need to study it carefully first. It is not constructed in the same way as other weather objects you may have modified. For example, the "Layered Weather Effects" comprises multiple objects with multiple states and image files in a mandatory (and carefully structured) Z-order. That being said, I encourage people to tweak it to their liking, which is not at all difficult if they're careful. But LGW pushes DX pretty hard, and sometimes you will encounter issues you'll need to work around.

*whew* that was long... I tried to explain everything... I hope it helped you, and anyone else reading who wants to tinker.

Cheers,

Will

Will,

I can't thank you enough for the thoughtful (and patient!) response.

I now understand the DX issues that you've pointed out, and I'm trying to work around them. FrameGlass is indeed the object that produces the "foggy" appearance and covers the zip text. Easily fixable with a context menu z-order change now that I know what's causing it. Version 2.21.029 has helped too - saving is much smoother and all I have to do to resolve the "type mismatch" error is re-enter the zip code. It seems also to have fixed the issue with frameglass showing in compact mode and being unresponsive. At least I haven't seen it since upgrading.

I'm still having trouble with reboots so I posted the steps to reproduce in the NGs. I'm also going to try stopping the scripts before I modify the object.

I actually don't want to make wholesale changes - your original object is too good for that! I really just wanted to use the overlay keys and customize the wx object and the radar object for my local area. Saving a theme and rebooting without script errors would be nice too. Your post was *very* helpful.

Thanks again!

Jeff

This object is awesome. I am having trouble with the clock portion. It does not display the correct time for my city. Which is in Arizona. Any suggestions?
Thanks,
Paul

Well this is a first. Umm, perhaps that's because it doesn't HAVE a clock portion? It's displaying the time the weather forecast was observed at the weather station, as reported by weather.com. Perhaps you might have noticed that the time only changed every 15 or 20 minutes??? You've probably seen the same "clock problem" with every other weather object...

Hey Will, a simple explanation would have been fine. You need to get out more and enjoy life you arogant SOB.

I'm very sorry I offended you! I've re-read what I wrote, and here's the "simple explanation" version:

"That's because it doesn't HAVE a clock portion. It's displaying the time with weather forecast was observed at the weather station, as reported by weather.com. Notice that the time only changes every 15 or 20 minutes. One sees the same "clock problem" with every other weather object."

I hope that makes you feel better. I certainly didn't mean to upset you, especially to the point you felt you needed to stoop to insults and harsh language. I write these objects (not to mention patches and answering questions) as a gift to the community, not so that you could be abusive if you became unhappy.

Hey, I see LookingGlass is "Download of the Day"! I suspect that may be a random-automated thing, but still nice.

Anyway, I thought people might like to know there will be an update to LookingGlass in a few days that fixes some issues and adds some cool new features (one I _think_ that no other weather object has...)