|
|||
|
I've experienced a problem using a combination of DirectX and runAndWait.
The main concept of my project is a platformgame where the user has to search and collect other games. I used DirectX.setDisplayMode(800,600,256) to make the game run more smoothly. When the user collects a game, the new game is started with the runAndWait-command. When i run the program without the directX, everything works well (slowly, but well). But when I'm using it with the DirectX, the second game starts, but the main game is frozen on my screen. Even with ALT-TAB, i can't switch to the second game.(I have to quit the second game with ALT-CTRL-DEL). I tried to use the 'Application.Behaviour.bAlwaysOnTop ' in my second game, but that doesn't work either. Is there a solution for this problem, or is this a limitation of DirectX. |
|
|||
|
It might be a limitation of DirectX. When the first app is running in DirectX mode, the main window of the second app is always under the first app. But the first app is waiting for the return of the second app, so you cannot control the first app while the second app is running.
The following code might work Code:
DirectX.restore(); Shell.runAndWait(...); DirectX.setDisplayMode(800, 600, 256); |
![]() |
Was this information helpful? Yes No
| Thread Tools | |
| Display Modes | |
|
|