Well, you could set an additional variable just before commanding the measure to execute, and do it in such a way to suggest that the skin is still focused, and of course set it back to the opposite value once the input has been entered or the input text has been dismissed. Then, when testing the focused state of the skin, you'd use both the OnFocusAction / OnUnfocusAction (if that's what you do) OR the value of that additional variable. Not sure of what and how exactly is your scenario, but you get the idea. After all, it's just some value telling you if the skin is focused, it doesn't have to come exclusively from the built-in Rainmeter events, you could "fake" it for this case via the additional variable...even if right now it is a problem for me
Statistics: Posted by Yincognito — Today, 9:03 pm — Replies 4 — Views 112