----- Original Message -----
> From: Mathieu Bouchard <[email protected]>
> To: Jonathan Wilkes <[email protected]>
> Cc: Roman Haefeli <[email protected]>; "[email protected]" <[email protected]>
> Sent: Monday, October 17, 2011 12:53 PM
> Subject: Re: [PD] Reason for different keyboard behavior of vanilla numberbox
> and nbx (Number2)
>
> Le 2011-10-17 à 09:37:00, Jonathan Wilkes a écrit :
>
>> We are talking about "Run mode" behavior for numberbox, and in
> "Run mode" <Return> doesn't mean "give up focus".
> So there's no problem.
>
> Sorry, you're mostly right. I hadn't woken up yet.
>
> But note that Ctrl+click in Edit mode does give the focus to a numberbox for
> edition, and then the numberbox does not give up focus on return.
Hmmm...
I think that's fine, because that is quite simply the behavior of numberbox.
Just because the user
entered the numberbox through a transient "Run mode" with <ctrl-click> doesn't
mean that
the user only wants to enter only one value.
It would be the same for an object that was a Pd-ish implementation of a tk
entry widget. In
"Edit mode" if you control-click the text area of the entry widget, it should
give you a cursor
and let you enter text, and do whatever it does when you click <Return>,
because that's the
"Run mode" behavior for that object.
If Pd started to have a large collection of GUI user input/edition objects
which use <Return>
as part of the input, it might be nice to add a standard key-binding to give up
that object's
"Run mode" focus. (Maybe <ESC>?)
-Jonathan
>
> ______________________________________________________________________
> | Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
>
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
