• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

Fullscreen Window Prohibits Screen Shot?

equant

Well-known member
Ok, I swear I posted this question early today, and can't find the orignal post anywhere, so I'm asking again....

I have an app that runs a full screen window that has no menubar and is not a screen saver. I can't get a screenshot to happen under system 6 (and I'm 80% sure I tried under system 9). Anyone know anything about this?

Thanks.

 

equant

Well-known member
It's from a programming book. An example of how to make a full screen application. There's event handling going on. Although the cursor is hidden, and in OS9 it takes the screen shot as soon as I quit tha app.... Hmm...

 

juan123

Well-known member
wow that is odd indeed... maybe the application has a function to take a screenshot within itself? For example Doom 3 which is a video game for OS X that runs full screen has a function to take a screenshot within itself. If I do the command that I would normally do, nothing happens... Keep us informed.

 

Kallikak

Well-known member
There must be a problem with your event loop. WaitNextEvent/GetNextEvent should handle FKEYs for you. How do you know event handling is going on? The System 9 behaviour sounds like the event is queued but not read by your application. What are you using for the event mask? What about sleep time?

If this is just some cut down example code, it may well be missed. I can guarantee that the screen capture is not disabled by using the whole display as your window.

Ken

 
Last edited by a moderator:

porter

Well-known member
I thought the screen capture was invoked by an FKEY resource.

Macs come with several FKEYs already installed by Apple. FKEY #1 ejects the floppy from the internal drive. #2 used to eject the floppy from the second floppy drive; now it probably does nothing, since Macs no longer even have floppy drive ports. #3 and #4 are for taking snapshots of the screen.
Are you calling WaitNextEvent or GetNextEvent?

Are you calling "SystemTask"?

 

equant

Well-known member
Kallikak and porter,

Yeah, you guys are right, what I assumed was a loop using WaitNextEvent was not. I haven't changed the code yet (Basilisk wasn't cooperating), but I'm sure that's indeed the problem.

Thanks.

 

porter

Well-known member
Kallikak and porter,
Yeah, you guys are right, what I assumed was a loop using WaitNextEvent was not. I haven't changed the code yet (Basilisk wasn't cooperating), but I'm sure that's indeed the problem.

Thanks.
Of course you will use Gestalt before you change the code to call WaitNextEvent ...?

 
Top