Layers.library V45 on the aminet

[Georg]

The problem here is that one cannot reliably call MoveWindow() from within the intuition input handler (which is responsible for the dragging the window, receiving the move movements and performing the actual layer movement as well, actually). My best guess is that MCP plays with the rather delicate semaphore hierarchy of intuition to avoid a deadlock, but then fails to cover the interactions between all the semaphores correctly, leaving some structures unlocked that should rather be locked, hence causing a conflict somewhere.

Intuition executes MoveWindow() asynchronously, so there are not many semaphores involved. But as said solid window moving commodities/tools (there are others like MultiCX) would typically call MoveWindow() from a helper task (or the main task), as otherwise while quickly dragging windows around there is no time for low pri app tasks to refresh simple refresh windows (until user stops dragging window for a moment) and you get a DPaint like brush-paint effect. Unless other hacks are used to for example force all windows to be smart refresh.

[Georg]

As for the ARexx script: if possible (and if you don't trust other tools) make it loop forever and move window to screen mouse coords and remove delay.

[guest11527]

As for the ARexx script: if possible (and if you don't trust other tools) make it loop forever and move window to screen mouse coords and remove delay.

This doesn't make any difference. As you say, MoveWindow is asynchron. It essentially builds up a message, and pools it up in the input queue of the intuition input handler. The input handler runs once per VBI, thus any attempt to run the window movement more often just pools up more messages, but does not create more work.

The problem here is, however, the interaction of the calling task through messages with the input handler. Thus, if you call MoveWindow from *within* the input handler, this might have undesireable side effects.

[TuKo]

Thomas, I tried the ARexx script and unfortunately it didn't trigger the bug. It seems to me bug is triggered when switching focus from one window to another.