ALLOW.BUTTON.EVENTS and GETREGION ?

[Ron Kaplan]

I have seen a number of calls to GETREGION that are preceded by ALLOW.BUTTON.EVENTS and in at least one case by SPAWN.MOUSE.

Does it ever make sense for mouse buttons to not be allowed if region sweeping is running in the mouse process?

That is, should GETREGION be changed to call ALLOW.BUTTON.EVENTS on entry and not leave that up to the caller?

[Larry Masinter]

you don't want to have two different processes each expecting the user to draw out a region (at least not on the same screen).

Once you get into GETREGION, do  you want to allow other processes to run?

I would be hesitant to make changes in the process interaction logic without a better model for what's going on.

https://LarryMasinter.net  https://interlisp.org

--
You received this message because you are subscribed to the Google Groups "Medley Interlisp core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lispcore+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/lispcore/804ADB8B-A7F9-4933-9DA4-33230F59D897%40post.harvard.edu.

[Ron Kaplan]

I tried (PROCESS.EVAL 'MOUSE '(GETREGION)) and it seems to work without a preceding call to ALLOW.BUTTON.EVENTS.

So there appears to be no reason for the hardcopy functions to call ALLOW.BUTTON.EVENTS before they call GETREGION.  That was a needless complexity that I will remove. 

[Nick Briggs]

What would happen if you did a hardcopy, were prompted for a region and let it go into idle, where you can only get out with a mouse click?  I think that’s the kind of scenario that allow.button.events is supposed to mitigate. 

Sent from my iPhone

On Dec 24, 2025, at 21:03, Ron Kaplan <ron.k...@post.harvard.edu> wrote:

I tried (PROCESS.EVAL 'MOUSE '(GETREGION)) and it seems to work without a preceding call to ALLOW.BUTTON.EVENTS.

To view this discussion visit https://groups.google.com/d/msgid/lispcore/021DB755-21A8-49F6-8CEC-1361FAFF26D1%40post.harvard.edu.