Common to triggers, actions and conditions is the "type" field, which, when tapped, opens the selection dialog.
Bind another gesture to this field: by pushing (long tap), the online resp. offline help page is opened.
Reason: having a button based shortcut to a component related information provision facility can allow future addition to linked knowledge tidbits which are otherwise lost in depth of time, forum or oblivion. So currently would that gesture have the same effect as the "?" at the end of the same line, but eventually allowing to provide different but related information without interfering with the existing help facility.
"type" field gesture for documentation provision
Moderator: Martin
Re: "type" field gesture for documentation provision
Sorry, I don't understand this request. What's the difference between the help button and the long-tap? Do you want to store your own notes and documentation for each component or where does the long-tap lead to?
Re: "type" field gesture for documentation provision
That's the past which hasn't been thought out in detail - current line of thought is: help text fragments are html, therefore is the help viewer a - possibly minimal - html viewer. The long tap gesture would therefore only display same help items as the "?" button because it is set to the same directory. But by changing that directory, a whole different set of documentation files could be accessed. In that case, it would probably be irrelevant whether those documents reside on the local machine, on a web server in LAN, or on internet.
What information would be accessed? For example, to my numerous messages concerning questions about our perceived limitations of Automagic components, many valuable tips and suggestions were received in return. Those can't be found anywhere else, neither in docs, nor in forum, and are bound to get lost. I'm sure other users made similar experiences. Or, one may figure out an unconventional but interesting use of a function, an action, or a noteworthy side effect which he wants to share with the community. Placing such information in the forum lacks the link from component to information - I'm not likely to explore the forum for possible information related to a function I'm just about to use. But I am much more prone to push the bar, bearing the function name, with the intention to view and peruse additional information, not found in the help text. As there exists some chicken and eggish situation - why carry such information together if no facility to access it exists / why provide such a facility if the information it its supposed to provide hasn't been carried together yet - having the method to access alternative and complementary documentation available, even though only already existing docs are accessed, but with a manageable path to replace it, may be just the kind of kick off which is needed to save and structure such information tidbits, rather than read and forget them.
Note to myself: put more periods into sentences.
What information would be accessed? For example, to my numerous messages concerning questions about our perceived limitations of Automagic components, many valuable tips and suggestions were received in return. Those can't be found anywhere else, neither in docs, nor in forum, and are bound to get lost. I'm sure other users made similar experiences. Or, one may figure out an unconventional but interesting use of a function, an action, or a noteworthy side effect which he wants to share with the community. Placing such information in the forum lacks the link from component to information - I'm not likely to explore the forum for possible information related to a function I'm just about to use. But I am much more prone to push the bar, bearing the function name, with the intention to view and peruse additional information, not found in the help text. As there exists some chicken and eggish situation - why carry such information together if no facility to access it exists / why provide such a facility if the information it its supposed to provide hasn't been carried together yet - having the method to access alternative and complementary documentation available, even though only already existing docs are accessed, but with a manageable path to replace it, may be just the kind of kick off which is needed to save and structure such information tidbits, rather than read and forget them.
Note to myself: put more periods into sentences.