I was initially only after "right" click detection in an XY menu, but a modifier key would work also.
If available, I'd probably only use one and that's if and when needed. Hi highend, I agree that that any more than 1 or possibly 2 modifiers will get out of hand and difficult to manage. I agree with most of what you are saying, but I don't think it's hurts anything to simply leave it alone. I don't think it's all that confusing to people who have been scripting for any length of time that get trigger is used for CTBs only though Don should make that clear in the help file. As a fatter of fact the help has states: "MiddleClick = 4 (planned)" Get trigger was also originally suppose to cover the middle mouse button, but Don said it would come later that can't be accomplished with the current CTB edit dialog box. Hi TheQwerty, I know right click of a CTB would not go away with get trigger departing, but some of us have used 'trigger' in a number of scripts, so it does mean back tracking to change who know how many scripts. While this still encourages developers to break standards to have different left/right-click menu actions it limits the damage they can do.ġ) It allows for the real intent triggering multiple actions from a single menu item.Ģ) It limits the total number of actions in a single item to 8 rather than 16 (or more if other mouse buttons were added).ģ) It doesn't encourage script authors to entirely ignore mouse or keyboard users - all actions are still accessible via either. If the ability to retrieve modifier keys is added I am also okay if XY converted right-click triggers into Ctrl+Left-Click (or similar). It could mimic SendKeys and use '+' (Shift), '^' (Ctrl), and '%' (Alt) or AutoHotkey which uses '!' for Alt instead and adds '#' for WinKey. Since we still do not have bit-operators I don't think it should return an OR-ed bit flag but rather a string of characters representing which buttons were held down. I approve of the idea of Get('TriggerModifierKeys') (or similar) returning info about any combination of Shift/Ctrl/Alt that were held when a script was started. I am against right-click detection within menus via Get('Trigger') - frankly I think Trigger should be removed, but that's a different topic. I know this is a big wish and this topic has been touched upon before, but I think it would be a such a very powerful addition to XY's scripting capability that it deserves to resurface again. For example a script could very easily program actions to simulate the actions of the user CTBs and XY built-in buttons for the both left and right mouse clicks simply by the mouse button clicked.
Essentially someone could program via scripting dual actions for a menu item similarly to what we can currently do with a CTB and get trigger, but this would expand that functionality way beyond that. If a right click of a mouse button detection is not possible or a coding nightmare, an alternative would be to detect if the user had a modifier key (e.g., control or shift etc.) held down while they clicked a mouse button. It would make scripting XY menus so much more powerful and open it up to so many new possibilities. In other words, be able to detect if the user has pressed a right mouse button in lieu of the normal left click. Hi Don, would it be possible to get a get 'trigger type' capability for a scripting menu item.
0 kommentar(er)
