Statistics: Posted by SylvainT — 30 Dec 2008, 22:08
]]>2008-12-25T17:19:48+02:002008-12-25T17:19:48+02:00https://brainmodular.org/forums/viewtopic.php?t=1235&p=6698#p6698Statistics: Posted by senso — 25 Dec 2008, 16:19
]]>
2008-12-25T15:55:26+02:002008-12-25T15:55:26+02:00https://brainmodular.org/forums/viewtopic.php?t=1235&p=6696#p6696 only usine... tnx
why I can't choose between present behavior of input fields (double-click and then edit while mouse must be still over this field, and then confirm pressing enter) and something "mouse-independent". I and many people I know are patching sitting in strange posiitions with their laptops (on the bed, on the flour) and must do acrobatic things to leave mouse in one position while editing some values with keyboard. sometime I need to try many times to edit one value because mouse is going out the editing field
The 'hide on exit' behavior is is no longer implemented in usine. I've just realized that it's not really necessary now, with the timer implementation. (by 'timer' I mean that the edit box disappears if there is no activity after 5 seconds)
why not to delete modules with simple press "delete" instead of "shift-delete" - its not fast-patching-friendly maybe let user configure thinks like that - there are more like this I think
Actually there is a Windows conflict between the 'del' in an edit box and the 'del' in a patch, so impossible to replace the 'shift del' by 'del'.
why I can't choose between present behavior of input fields (double-click and then edit while mouse must be still over this field, and then confirm pressing enter) and something "mouse-independent". I and many people I know are patching sitting in strange posiitions with their laptops (on the bed, on the flour) and must do acrobatic things to leave mouse in one position while editing some values with keyboard. sometime I need to try many times to edit one value because mouse is going out the editing field
It's a protection for the live. I'll create an option in the setup to disable this option.
why not to delete modules with simple press "delete" instead of "shift-delete" - its not fast-patching-friendly maybe let user configure thinks like that - there are more like this I think
]]>2008-12-25T11:18:59+02:002008-12-25T11:18:59+02:00https://brainmodular.org/forums/viewtopic.php?t=1235&p=6685#p6685why I can't choose between present behavior of input fields (double-click and then edit while mouse must be still over this field, and then confirm pressing enter) and something "mouse-independent". I and many people I know are patching sitting in strange posiitions with their laptops (on the bed, on the flour) and must do acrobatic things to leave mouse in one position while editing some values with keyboard. sometime I need to try many times to edit one value because mouse is going out the editing field
second: why not to delete modules with simple press "delete" instead of "shift-delete" - its not fast-patching-friendly
maybe let user configure thinks like that - there are more like this I think
Statistics: Posted by SylvainT — 30 Dec 2008, 22:08
]]>2008-12-25T17:19:48+02:002008-12-25T17:19:48+02:00https://brainmodular.org/forums/viewtopic.php?t=1235&p=6698#p6698Statistics: Posted by senso — 25 Dec 2008, 16:19
]]>2008-12-25T15:55:26+02:002008-12-25T15:55:26+02:00https://brainmodular.org/forums/viewtopic.php?t=1235&p=6696#p6696 only usine... tnx
why I can't choose between present behavior of input fields (double-click and then edit while mouse must be still over this field, and then confirm pressing enter) and something "mouse-independent". I and many people I know are patching sitting in strange posiitions with their laptops (on the bed, on the flour) and must do acrobatic things to leave mouse in one position while editing some values with keyboard. sometime I need to try many times to edit one value because mouse is going out the editing field
The 'hide on exit' behavior is is no longer implemented in usine. I've just realized that it's not really necessary now, with the timer implementation. (by 'timer' I mean that the edit box disappears if there is no activity after 5 seconds)
why not to delete modules with simple press "delete" instead of "shift-delete" - its not fast-patching-friendly maybe let user configure thinks like that - there are more like this I think
Actually there is a Windows conflict between the 'del' in an edit box and the 'del' in a patch, so impossible to replace the 'shift del' by 'del'.
why I can't choose between present behavior of input fields (double-click and then edit while mouse must be still over this field, and then confirm pressing enter) and something "mouse-independent". I and many people I know are patching sitting in strange posiitions with their laptops (on the bed, on the flour) and must do acrobatic things to leave mouse in one position while editing some values with keyboard. sometime I need to try many times to edit one value because mouse is going out the editing field
It's a protection for the live. I'll create an option in the setup to disable this option.
why not to delete modules with simple press "delete" instead of "shift-delete" - its not fast-patching-friendly maybe let user configure thinks like that - there are more like this I think
]]>2008-12-25T11:18:59+02:002008-12-25T11:18:59+02:00https://brainmodular.org/forums/viewtopic.php?t=1235&p=6685#p6685why I can't choose between present behavior of input fields (double-click and then edit while mouse must be still over this field, and then confirm pressing enter) and something "mouse-independent". I and many people I know are patching sitting in strange posiitions with their laptops (on the bed, on the flour) and must do acrobatic things to leave mouse in one position while editing some values with keyboard. sometime I need to try many times to edit one value because mouse is going out the editing field
second: why not to delete modules with simple press "delete" instead of "shift-delete" - its not fast-patching-friendly
maybe let user configure thinks like that - there are more like this I think