SCANLINE EFFECTS...

[iamaboringperson]

If scanline movement could be kept from moving rapidly on screen and stayed at the bottom of screen, this would not happen on RTG screens.

I can't really understand what you are on about...
Do you know how a raster display works?

[iamaboringperson]

@FaLLeNOnE

I know what you are trying to say by 'scanline' now...

You seem to misunderstand the term.
A television usually has 625(PAL), or 525(NTSC) scanlines which are interlaced.
Lets use PAL as an example of what happens:
PAL uses 25 frames per second. Which is made up of 2 'feilds' per frame. So there are 50 of these feilds per second.
Each feild is drawn by 312.5 lines down the screen(some are hidden - sortof).
Each one of these lines is a 'scanline' or 'raster (line)'.

What you seem to be talking about with the camera, is where the camera and TV are slightly out of sync.
The part that looks abit wobbly when you shake the camera from side to side, is not called a scanline, it moves up or down because both devices are not starting the drawing of the display at the exact same time. One starts to draw its display while the other is in the middle of its.
If the gap is moving up or down, then they are not at the exact same frequency, they both might be about 50Hz(interlaced) (or 60Hz for NTSC), but they are slightly different.

I hope this helps clarify things... :-)

[iamaboringperson]

@Lando

ahhh! ;-)
Good question! :-)

The Amiga was certainly designed for CRT's!
The beam position is worked out using timers in the Amiga custom chips.
A sync signal is then sent to the monitor, and the monitor syncs to this signal(which baiscally says that when the signal says 'go', the monitor starts at the very top)
An LCD screen is usually made to work with this same signal. There is no real scan line, but the monitor still knows what to do with the sync signal. Just like it does with the other parts of the signal(or other signals).

[iamaboringperson]

I know from my own experiments that some of the OS functions such as "WaitTOF()' don't seem to work as expected with my BVision card. WaitBOVP() seems to work OK, however.

I was thinking about WaitTOF(), but what I'm wondering is to which monitor does it refer?
If a person is using a two(or more) monitor setup, or otherwise has multiple screens of different resolutions, which one does it check?
I can't see how it knows which monitor the program is using at current.
This is one function that needs some updating - I think.