Just downloaded 4.03 and the bug preventing widgets from closing on Mac OS X has not been fixed yet.

I have seen widgets moved around periodically, usually this occurs when changing screen resolution or when going from multiple monitors to a single monitor. When I use a second monitor I avoid putting widgets onto it.

Regards

Had an issue where this widget was running but somehow was forced offscreen. Debug showed a main window offset of 137.

Simpliest way to get it back was close the widgets widget then delete the registry value for the position and restart the widgets widget. This will put it back at the default position.

Navigate using regedit to:
HKEY_CURRENT_USER\Software\Yahoo\WidgetEngine\Widgets\The Widgets Widget\Windows\main_window

and delete the positions value (you must close the widgets widget befo…re deleting, otherwise it will save the current position offscreen again).

This was in XP home SP2 using version 2.38 of the widget on YWE 4.0.2 (build 175) More

Y!WE 4.0 and 4.01 have a bug in the close widget logic that is preventing The Widgets Widget from closing widgets on a Mac. A bug report has been filed and hopefully an upgrade of the engine will correct it. I am not going to modify the Widget to try to program around the bug.

Yahoo! Widget Engine 4.0 has broken The Widgets Widget on Mac OS 10.4. Groups of widgets can be opened but will not close. It is working properly on Windows XP-SP2. I'll look into it and release an update as soon as possible.

ssadams1111,

Thanks for the info. I'm glad it is working. A few questions about what you did:
- "several reinstalls" - reinstalling just Yahoo! Widget Engine or something more?
- "cleared the registry" - how did you do this? With regedit? Some other way? Did this procedure negatively affect any of your other installed applications?
- "Application Data cache" - where is that and how did you clear it?

It does sound like the problem has something to do with …the registry updates done when Yahoo! Widget Engine is installed. That makes some sense because the COM command uses the registry to connect to YWE and that seems to be the line that is failing.

Regards More