OpenWindowedScreen

dmoc · Post by **dmoc** » Tue May 06, 2003 3:09 pm

When using this with the AutoStretch flag the actual screen (PB's not Window's) is clipped by a pixel (or two) on the right and bottom. This is a bug I think. To avoid this problem I don't use AutoStretch but instead set the screens dimensions explicitly. Next problem: without resorting to Windows callback proc there seems no way to detect a resize event. PB's events list does not include it and PB appears to filter the event out.

I'm attempting to use as much inbuilt PB functionality as possible since I want to migrate my app soon (hopefully, I wish) to Linux. I'm also aiming for an application that allows the user to switch (dynamically) between windowed and fullscreen.

Edit: I must have been looking for the wrong event as PB *is* routing #WM_SIZE.

fsw · Post by **fsw** » Tue May 06, 2003 4:56 pm

Keep in mind that the OpenWindowedScreen function under Linux acts different.
Under Windows you have to open up a Window with OpenWindow and than you can do OpenWindowedScreen .
Under Linux it's not necessary to open a Window first ( OpenWindowedScreen has it's own Window) . So what to do with the second Window (if you use the same code for Windows/Linux) ?
You could use a Delay Command than the OpenWindow related Window will not show up. Nice feature [bug?] isn't it?
@ this point PureBasic Windows/Linux code is not 100% the same - but I would expect it, as long I don't use OS-API.

dmoc · Post by **dmoc** » Tue May 06, 2003 5:30 pm

Thanks for the info fsw. The aim is eventually for only a Linux version but to cover all bases I'll probably use compiler directives until that point. Yes, it would be nice if PB's platform differences were ironed out