Thread View: comp.sys.amiga.tech
1 messages
1 total messages
Started by Ron Tarrant
Sat, 22 Dec 1990 02:05
Re: Simple Overscan Display
Author: Ron Tarrant
Date: Sat, 22 Dec 1990 02:05
Date: Sat, 22 Dec 1990 02:05
24 lines
1463 bytes
1463 bytes
> BAXTER_A@wehi.dn.mu.oz writes: > > This CAN NOT be derived from ANY system information. Under WB2.0 you can find > out the "text" and "overscan" sizes of the screen as selected by the user- > which are supposed to represent what you want to know, and these are used to > set the workbench size. But that in no way stops the user choosing to have > a one inch black boarder all round the active screen, which you won't know > about. > > An alternative is just to open an overscanned screen (just use > overdimensional > values when specifying screen size) and expect the user to reset the monitor, > but most people on finding the screen cut off by the bezel will assume > you are a shit programmer and not use your program. > > Regards Alan If I were writing a word processor or a spreadsheet I would expect people to think things like that. However, I'm writing a video tool. If a video tool DOESN'T do overscan then your comment about s*** programmers would apply... in spades! -Ron Tarrant a976@Mindlink.UUCP
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads