It works again --- YAY!!

@qmaster101

As soon as I was aware of the problem a newer version was sent to Yahoo, the approval process takes about a week even if its a regular update, 1.2 was sent and Im already working on 1.3 (scheduler :).

As you may know they are quite busy with YW 4.0 since it has some minor issues (check the forums, some widgets dont work as expected :) Version 1.2 its fixed to work as expected.

"Also, when pressing CTRL-M, the timer sets delay to come out of standby - - not the delay to go int…o standby."

About the keyboard shortcut, it is intended as most keyboard actions to act instantly so there is no delay.
If you want to double click and have the same instant effect you can set the delay to zero, but it is possible that a small mouse move will bring the screen back so I've added a few ms delay.

The delay set in preferences has nothing to do with the time it takes your system to react and bring back the screen, try different settings and you'll see that.
More

@Cicerone Pavaloi
Thanks for your tips Cicerone! The "Main.visible=true" after all resizing was implemented on 1.3 (working on it now, trying to add a scheduler and update notifier too :)

However, can you tell me if just removing minimumVersion="3.0" makes it work under 2000?
I've tried on XP and it fixes the hidden issue, however I took note of your suggestions, now <image> is enclosed into <window> :)

BTW you can reach me at the forums, nick "grbsoft&…quot;

New version has been sent to approval, it might time some time so if you are in a hurry drop me a line there in the forum and I will send you the fixed version. More

More...
In onFirstDisplay trigger you have:
Main.hOffset = 10 + screen.availRight;
Screen object has no availRight property... You wanted availLeft probably? For right you need to use availWidth, but adding 10 to this will place the window off screen...
And the delay is not happening when hotkey is used. If this is what you wanted, then maybe is better to specify that the delay preference is for double-click only (in the description of the preference).
Other than that, your widget is running like a charm. Keep up the good work.

Hi.
I'm guessing that the "no show" bug have something to do with the fact that the image object "monitor_pix" has no parent window... Some widget engine on some operating system may cope with this and assign the image to the first window it finds, but on my win 2000, running YWE 3.1.4, this is not happening.
Two ways to fix this:
1: move the end tag </window> after the end tag </image>, so the engine will create the image as a child of the window;
2: in onL…oad trigger include this line
monitor_pix.window = Main;
Put it after the call to doChange(), so the user don't see the image changing its size if smaller than 100%. More