http://www.blitzbasic.com/Community/posts.php?topic=44366
Use that concept, and use BlitzSys (which I can't find, sorry :( If I ever do I'll post it up for easy reference... and I'll email it to you if you want) to find the window x y position without the use of crazy pointer stuff which blitz doesn't support. The embedded application would have to be a child window of the main window, with the start window removed using one of the many blitz start window removal tools, and it can run anything you want it to that blitz can possibly run. To kill it off, use api_destroywindow in user32 to destroy the child window (the child window is found like this:
I have an example of this "nifty" solution as used in my application posted here: http://www.blitzbasic.com/Community/posts.php?topic=45982
No, the window will not lose focus, because as long as it has the style attribute "WS_POPUP" or something similar, the child will stay on top of its parent (in fact, it seems to stay on top of its parent no matter what).
It's all a bit weird to get used to, but once you do, it's all very straight-forward and useful.
I bet if you were really crazy and had loads of time to search through the win32 command reference (http://www.mentalis.org/agnet/apiguide.shtml) you could actually make the embedded window force the main window to animate...
Use that concept, and use BlitzSys (which I can't find, sorry :( If I ever do I'll post it up for easy reference... and I'll email it to you if you want) to find the window x y position without the use of crazy pointer stuff which blitz doesn't support. The embedded application would have to be a child window of the main window, with the start window removed using one of the many blitz start window removal tools, and it can run anything you want it to that blitz can possibly run. To kill it off, use api_destroywindow in user32 to destroy the child window (the child window is found like this:
Const GW_CHILD = 5 api_GetWindow(hWnd,GW_CHILD))
I have an example of this "nifty" solution as used in my application posted here: http://www.blitzbasic.com/Community/posts.php?topic=45982
No, the window will not lose focus, because as long as it has the style attribute "WS_POPUP" or something similar, the child will stay on top of its parent (in fact, it seems to stay on top of its parent no matter what).
It's all a bit weird to get used to, but once you do, it's all very straight-forward and useful.
I bet if you were really crazy and had loads of time to search through the win32 command reference (http://www.mentalis.org/agnet/apiguide.shtml) you could actually make the embedded window force the main window to animate...