Posted: Mon Nov 19, 2001 9:36 pm
Restored from previous forum. Originally posted by Franco.
I think that a ViewScreenArea command would be a great thing.
When you code something like:
you are able to create a screen with the resolution of 1600x1200.
Now you have the intention to create a jump and run game and with the command
you are able to view only 1 quarter of your screen und jump around and when you go to the an edge you switch to the next 'Area' without moving all objects or to create new ones.
You can also leave your 'Mario' allways in the middle of your window and smoothly move the environment.
Or you have the intention to create a CAD files viewer (gerber files) like I do, you are able to zoom in or out, to pan your view to any side and so on (without move or resize your objects around). PureBasic must be fast enough to have a smooth panning or zooming.
And the best of all, with a minimized amount of code!
This would be excellent.
BTW: does anybody know the maximal resolution of a screen? I suppose there must be one...
Have a nice day...
Franco
I think that a ViewScreenArea command would be a great thing.
When you code something like:
Code: Select all
If OpenWindow(0,0,0,1024,768, #PB_Window_SystemMenu, "Screen Test Window")
InitSprite(0)
OpenWindowedScreen(WindowID(),10,68,1600,1200,1,10,10)
...
Now you have the intention to create a jump and run game and with the command
Code: Select all
ViewScreenArea(0,0,800,600)
You can also leave your 'Mario' allways in the middle of your window and smoothly move the environment.
Or you have the intention to create a CAD files viewer (gerber files) like I do, you are able to zoom in or out, to pan your view to any side and so on (without move or resize your objects around). PureBasic must be fast enough to have a smooth panning or zooming.
And the best of all, with a minimized amount of code!
This would be excellent.
BTW: does anybody know the maximal resolution of a screen? I suppose there must be one...
Have a nice day...
Franco