I've been considering a separate but communicating popup routine in my WP project. It would allow a resize of the doc, without affecting the size of the popup. It would also save me making a moving popup function. However, since this method shells to run an additional separate instance of the program, there is a bit of a lag factor on slower computers.
I could use Windows API to maintain focus, and even get rid of the top Windows border on the popup. Right now, I'm just fiddling with some things, beginning with appearance, which isn't too bad.
Note: This demo
won't create any files on your system. It just references itself, via an error trap for an open the exe file for input with a LOCK in place. That creates a trapped error 70, permission denied. This method is fine for this demo, but only allows the user to press the popup key once. An actual temp file method would be employed, to solve that situation, if I go forward with this concept. I've already done similar projects with network handling of shared files over multiple computers.
Now maybe there are some new QB64 commands I'm unaware of that can do something similar to this already?Anyway, to get this to work, you have to
save it as myprog22xyz.bas and let the QB64 IDE compile it into
myprog22xyz.exe. If you fail to do so, no popup will occur when you
press the F3 key.Oh, the "Hello Heaven" message is just a joke. Although considering the time it might take me to put this all together, it might also be a prophecy.
shell1% = -1
er1% = 0
PRINT "Unexpected error, code ="; er1%:
END
handler:
Pete