I found that site while, searching, but I didn't notice the widget download the first time around. Anyway, I tried it out, and the new method works perfectly. Thanks for your dedication, and kudos for being so quick to correct things.

My apologies, but the double-click to force close widgets added in version 2.36 caused some problems. The Engine doesn't handle objects with both an onMouseUp and an onMultiClick handler the way I thought it would. So I've now updated to version 2.37 which will force a group of widgets to close if you hold down the shift key when clicking on the group name. So if widgets keep reopening after you close them, try shift-click on the group name.

Regards.

For all those experiencing the problem on Windows of widgets reopening automatically after closing. First, thanks for your patience and letting me know about the problem. Second, I've made a modification and uploaded version 2.36 to allow a work-around for the problem. The work-around is to double-click the button to close the widgets rather than single-click. I will continue to try to make the single-click method smart enough to deal with all Windows configurations and flavors, but unti…l then double-clicking should work. I hope this helps. Version 2.36 is available now at my website and should be available in the gallery in a few days.

Regards. More

(Continued from previous post)
In my testing using COM causes crashes when trying to get the list of running widgets, which is why I used the registry query method. I'll see if there are any other ways, but for now I'm afraid if you are using Windows and are seeing the widgets reopen after closing then The Widgets Widget is not compatible with your system.

Regards.

OK, I now have a theory as to what may be causing the reopening problem on Windows. I'm not sure how to fit it yet, but having a testable theory is the first step. When you click on the button the Widget issues a command to get the list of currently running widgets, on a Mac this is done with the ps command, on Windows it is a query to the registry. Then it tests each widget in the group list to see if it is also in the run list. If all widgets in the group list are also in the run list t…hen it closes them all. If a widget in the group list is NOT in the run list then it starts the widget. If you start a widget that is already running then YWE! will close the running widget and then reopen it. This is what I think is going on: On some Windows machines the registry query is not returning the correct list of running widgets, although it does on my Win XP Pro machine. I don't know of a reliable alternative way to get the running widgets. In my testing using COM causes crashe More