@bplus You're welcome, anytime!
@Spriggsy
I tried your method, and yep, it works the same as mine, only yours takes advantage of using QB64 keywords to do what the API calls do. So I think what we have here is a situation where Windows never accounted for another window transferring control to another window. In other words the developers expect users to click a window to activate it. What bugs me is that the developers coded the system to activate a window that is moving from the task bar back to the desktop. That means there must be some command to activate it after it gets restored.I would think that would be available for use as API users, but so far, I can't figure out if I'm missing something or if such a command was simply not made public.
Thanks for having a look. Yep, great minds think alike alright, which means Bill's in real trouble!
Pete
@Spriggsy
I tried your method, and yep, it works the same as mine, only yours takes advantage of using QB64 keywords to do what the API calls do. So I think what we have here is a situation where Windows never accounted for another window transferring control to another window. In other words the developers expect users to click a window to activate it. What bugs me is that the developers coded the system to activate a window that is moving from the task bar back to the desktop. That means there must be some command to activate it after it gets restored.I would think that would be available for use as API users, but so far, I can't figure out if I'm missing something or if such a command was simply not made public.
Thanks for having a look. Yep, great minds think alike alright, which means Bill's in real trouble!
Pete