Hi IVAN,

 you wrote at 24.11.98  01:13 to HERBERT ROSENAU:
 
 IT>      When I dragged windows around, the beeping simply stoped!

This depends on your hardware. Dragging of a full sized window is a
resource (cpu) consuming operation in high priority. Even the kernel - and
drivers runs multithreaded and with different priority.

Try the operation on different processors (i486 -> P2/450 with different
memory on board and you see the difference.

Play on themn with

MAXWAIT=x (x = 1 to 3)
IOPL=YES	or NO

in config.sys and you'll find on the same hardware different behavior.

[...]
 HR>> The WPS itself ist locked until the view is shown but the program
 HR>> you has started before is ready for work.

 IT>  Tried this, and it works as you decribed it, but still there is a
 IT>  noticeable period when you cannot switch the focus to another
 IT> window.

This is the time the mouse message is active (the system queue is blocked).
The other time results on posted messages inside and between PM and WPS. In
WPS 1.0 was the whole action directly depending on the initial mouse
message and the whole desktop was locked the full time until the window was
fully painted.

Since OS/2 1.1 exists a rule for PM programmers: a message is to handle in
1/10s. If this is impossible the handing is to shift to another thread.
This rule should free the system message queue in short time. An other way
to become the system queue unlocked is POSTING a WM_USER to the same window
- but NOT for truly time consuming messages! You my create other threads
and post them the messages received from system queue. 


Tschau/Bye

Herbert


--- Sqed/32 1.14/development  22: