Prevent user from moving my Screen

[Photon]

I open it with a new screen struct, but I haven't seen any pertinent flags.

I can think of a few creative alternatives:

1. Protect the Screen from mouse events by "unfocusing" it (while still being shown and frontmost)
2. Actually somehow hide it from the Screen list (while still being active and frontmost)
3. Prevent clicks on the title bar on mouse click.
4. Prevent the mouse from moving the pointer. Forbid() does, but eventually control is handed back.
5. Move the pointer back as much as it has moved since last time.
6. Move the Screen back as much as it has moved since last time.

I realize they all read like an excellent prank application but it's for a utility.

[Thomas Richter]

There is none. You can place a window on top of the drag bar, but you can still drag the screen then with the right Amiga key and the left mouse button.

[Photon]

Maximized window could work. For my purposes, only left-click+drag needs be stopped. I'd have to clear it immediately to draw my stuff, and not waste memory.

Speaking of moving the pointer, can I do so programmatically? If not, then can I send keyboard events to move the pointer?

Just thought of another prank, SetPointer() with an offset hotspot. Won't help much, maybe a little.

[koobo]

You could set up an input handler (with input.device) with a very high priority, then intercept all events and remove the ones that are related to dragging your specific screen

[hooverphonique]

Originally Posted by Photon

Speaking of moving the pointer, can I do so programmatically? If not, then can I send keyboard events to move the pointer?

Yes, using input.device, you can inject pointer move events.

[Photon]

Thx guys, will experiment.

Probably the best option would be to cancel mouse movement. The clicks themselves would then do nothing. Maybe save and restore mouse X/Y counters before/after Forbid/Permit.

[mark_k]

On Kickstart 3.0+ you could use the SA_Draggable and SA_Exclusive tags?

[No.3]

Originally Posted by Photon

...it's for a utility.

for what OS version? As with OS 3+

	SA_Draggable:  ti_Data is a boolean.  Set to FALSE if you
	    wish your screen to be non-draggable.  This tag should be
	    used very sparingly!.  Defaults to TRUE.  For child screens
	    (see SA_Parent, SA_FrontChild, and SA_BackChild) this tag
	    has a slightly different meaning:  non-draggable child
	    screens are non-draggable with respect to their parent,
	    meaning they always drag exactly with the parent, as
	    opposed to having relative freedom.  Also see
	    ScreenPosition().  (V39)

[Photon]

I support KS1.2-3.1+ with the utility. If something is impossible or difficult I will make exceptions for all but 1.3 and 3.1. So then my goal wouldn't be achieved on 1.3. But great that they added it.

[Thomas Richter]

SA_Draggable is probaby what you want, or maybe not quite what you want. The problem is that it also stops autoscroll screens from scrolling (if I recall correctly). If autoscroll is not an option for you, then go for it.

[Thomas Richter]

Originally Posted by koobo

You could set up an input handler (with input.device) with a very high priority, then intercept all events and remove the ones that are related to dragging your specific screen

Note that there are roughly two positions where an input handler could sit: Upfront the intuition handler, and below the intuition input handler. Above the intuition input handler, all a custom input handler sees are raw mouse moves bare any position information with only relative movements, and bare any scaling to screen coordinates. Below the intuition input handler, you do receive coordinates, but it is too late there to intercept intuition.