Re: menu buttons and showname
Agreed. Which brings me back to the point that when the label of a popup menu is empty there ought to be some default behavior like displaying the tootTip or a property containing a value the developer can set. I think we are all agreed that what it ought NOT to do is display the object name. Workarounds are plentiful, but as I stated before this is not about a workaround, it is about a control that doesn’t need workarounds to function as you might expect. Bob S On Jul 6, 2015, at 13:04 , Scott Rossi sc...@tactilemedia.commailto:sc...@tactilemedia.com wrote: Hi Bob: I would propose that empty is not an informative value for a user. Something like no selection or a call to action Select an option is going to be more helpful than an empty line. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
New copier device. Popup menu of manufacturers. I want user to explicitly pick a manufacturer, not just ignore the manufacturer that is there. I set it to empty and then check for empty before saving the data. Bob S On Jul 2, 2015, at 20:07 , Kay C Lan lan.kc.macm...@gmail.commailto:lan.kc.macm...@gmail.com wrote: I still can't invisage a situation where you'd want an empty option button. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
Hi Bob: I would propose that empty is not an informative value for a user. Something like no selection or a call to action Select an option is going to be more helpful than an empty line. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 7/6/15, 12:55 PM, Bob Sneidar bobsnei...@iotecdigital.com wrote: New copier device. Popup menu of manufacturers. I want user to explicitly pick a manufacturer, not just ignore the manufacturer that is there. I set it to empty and then check for empty before saving the data. Bob S On Jul 2, 2015, at 20:07 , Kay C Lan lan.kc.macm...@gmail.commailto:lan.kc.macm...@gmail.com wrote: I still can't invisage a situation where you'd want an empty option button. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
There are all kinds of workarounds for this. What is being discussed is why we need workarounds in the first place. Bob S On Jul 3, 2015, at 05:25 , David Epstein dfepst...@comcast.net wrote: “Set the label of button myBtn to space” makes an option button appear blank but does not interfere with a user’s subsequent choice of an option. While disabling the button or hiding the button are other ways of making clear that no option is in effect, an able but blank option button means that an option can be put into effect in one step, not requiring some other action that enables or shows the button. David Epstein ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
“Set the label of button myBtn to space” makes an option button appear blank but does not interfere with a user’s subsequent choice of an option. While disabling the button or hiding the button are other ways of making clear that no option is in effect, an able but blank option button means that an option can be put into effect in one step, not requiring some other action that enables or shows the button. David Epstein ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
Peter, I agree with the other here that the behaviour is as I'd expect and works the way I want it to. Can you better explain what it is you are after? Is it you have a button named Make a Choice and it's dynamically filled with 0 to umpteen choices, but regardless of whats in there, OR what a user chooses, you always want the button to return back to Make a Choice displayed? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
On 7/1/2015 8:52 PM, Peter Haworth wrote: The showName property needs to be true for the the user's selected choice from, for example, an option menu to be displayed. First problem - that's the label not the name. But if the text of the menu happens to be empty, its name is displayed instead of empty which normally isn't something you want to happen. The general rule is as the dictionary says: if showname is true and the object has a label, the label is displayed. Otherwise the name is displayed. But option button have dynamic labels that change to reflect the current selection. If there is no text in the button at all, then there can be no selection and therefore there can be no label. Since there is no label, its name is displayed. You'd think combo boxes would do the same thing, but those are a sort of hybrid field/button object and the so-called label portion responds like a field, where empty really can be empty. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
Yep, that's one of the things I've done. On Thu, Jul 2, 2015, 7:54 AM Randy Hengst iowahen...@mac.com wrote: Have you tried adding a blank line to the list of options? I’ve done it that way before… then just set the menuHistory of that option button to the line that is blank. be well, randy Randy Hengst www.classroomFocusedSoftware.com On Jul 2, 2015, at 9:46 AM, Peter Haworth p...@lcsql.com wrote: No, I simply want an option menu with empty text display an empty label, not its name property. As mentioned in the original post, I do that now by setting showname to false if the text is empty. On Wed, Jul 1, 2015, 11:29 PM Kay C Lan lan.kc.macm...@gmail.com wrote: Peter, I agree with the other here that the behaviour is as I'd expect and works the way I want it to. Can you better explain what it is you are after? Is it you have a button named Make a Choice and it's dynamically filled with 0 to umpteen choices, but regardless of whats in there, OR what a user chooses, you always want the button to return back to Make a Choice displayed? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
Peter Haworth wrote: So my technique of setting showname to false if the text is empty is the only way round this? Also, you can have a label for an option menu with empty text. Try setting the text of an option menu to empty, then use the message box to set its label to some value. With the OS X HIGs not nearly as complete as they used to be I can no longer find the relevant section on this, but I believe most HIGs suggest that we avoid giving the user the impression the control may be broken by replacing empty items with some explanation of why it's empty, or perhaps a disabled item simply saying None. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
No, I simply want an option menu with empty text display an empty label, not its name property. As mentioned in the original post, I do that now by setting showname to false if the text is empty. On Wed, Jul 1, 2015, 11:29 PM Kay C Lan lan.kc.macm...@gmail.com wrote: Peter, I agree with the other here that the behaviour is as I'd expect and works the way I want it to. Can you better explain what it is you are after? Is it you have a button named Make a Choice and it's dynamically filled with 0 to umpteen choices, but regardless of whats in there, OR what a user chooses, you always want the button to return back to Make a Choice displayed? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
Have you tried adding a blank line to the list of options? I’ve done it that way before… then just set the menuHistory of that option button to the line that is blank. be well, randy Randy Hengst www.classroomFocusedSoftware.com On Jul 2, 2015, at 9:46 AM, Peter Haworth p...@lcsql.com wrote: No, I simply want an option menu with empty text display an empty label, not its name property. As mentioned in the original post, I do that now by setting showname to false if the text is empty. On Wed, Jul 1, 2015, 11:29 PM Kay C Lan lan.kc.macm...@gmail.com wrote: Peter, I agree with the other here that the behaviour is as I'd expect and works the way I want it to. Can you better explain what it is you are after? Is it you have a button named Make a Choice and it's dynamically filled with 0 to umpteen choices, but regardless of whats in there, OR what a user chooses, you always want the button to return back to Make a Choice displayed? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
So my technique of setting showname to false if the text is empty is the only way round this? Also, you can have a label for an option menu with empty text. Try setting the text of an option menu to empty, then use the message box to set its label to some value. On Wed, Jul 1, 2015, 11:18 PM J. Landman Gay jac...@hyperactivesw.com wrote: On 7/1/2015 8:52 PM, Peter Haworth wrote: The showName property needs to be true for the the user's selected choice from, for example, an option menu to be displayed. First problem - that's the label not the name. But if the text of the menu happens to be empty, its name is displayed instead of empty which normally isn't something you want to happen. The general rule is as the dictionary says: if showname is true and the object has a label, the label is displayed. Otherwise the name is displayed. But option button have dynamic labels that change to reflect the current selection. If there is no text in the button at all, then there can be no selection and therefore there can be no label. Since there is no label, its name is displayed. You'd think combo boxes would do the same thing, but those are a sort of hybrid field/button object and the so-called label portion responds like a field, where empty really can be empty. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
Good point. For lots of reasons, the names of my option menus aren't suitable for display to a user. Maybe the cleanest thing to do then is, if the text of the menu is empty, set its label as suggested by Richard. I like that. Most of the menus in question are under the control of a behavior so this is easy to implement. On Thu, Jul 2, 2015, 8:28 AM Richard Gaskin ambassa...@fourthworld.com wrote: Peter Haworth wrote: So my technique of setting showname to false if the text is empty is the only way round this? Also, you can have a label for an option menu with empty text. Try setting the text of an option menu to empty, then use the message box to set its label to some value. With the OS X HIGs not nearly as complete as they used to be I can no longer find the relevant section on this, but I believe most HIGs suggest that we avoid giving the user the impression the control may be broken by replacing empty items with some explanation of why it's empty, or perhaps a disabled item simply saying None. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
Don't think you're missing anything. The example of table/column menus doesn't illustrate the original question I had since it's pretty much impossible to have a db without tables or a table without column. Maybe a better example of the empty menu might be one menu with a list of customers and a second menu of invoice numbers for the selected customer. It's possible that the selected customer would not have any invoices yet so the second menu would be empty. Once again, no call to action but I like the idea of displaying No invoices or something similar. Pete lcSQL Software http://www.lcsql.com Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and SQLiteAdmin http://www.lcsql.com/sqliteadmin.html On Thu, Jul 2, 2015 at 1:17 PM, Scott Rossi sc...@tactilemedia.com wrote: As far as there being a correct type of control, that's open to endless debate. :-) From what you describe, there doesn't seem to be a need for a call to action -- this was suggested simply to address the case that a selection MUST be made for things to work. Since this doesn't seem to be relevant in your situation, I would imagine you'd display a default option as the control label. The bigger issue is why you have an empty option at all. If that's a setting that a user can implement, the option should read something like no selection or empty or similar. If the empty value is something pulled from a table that can't be acted upon, there's no need to include it in the list of options. As always, I may be missing something. :-) Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 7/2/15, 12:59 PM, Peter Haworth p...@lcsql.com wrote: Interesting observation Scott. Makes me wonder if I'm actually using the correct type of menu. For example, I might have an option menu which lists the names of tables in a database and another one that lists the columns in the selected table. There's no call to action in that situation (other than to pick a table and a column), so is an option menu the correct type of control according to HIG? On Thu, Jul 2, 2015 at 10:00 AM Scott Rossi sc...@tactilemedia.com wrote: Often, this type of control has a call to action such as Choose an item, as opposed an indication No selection. It depends on the context of your control. If a selection is required in your set up, the call to action is more communicative. Otherwise, if No selection is a valid selection then that type of message should work. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 7/2/15, 8:47 AM, Peter Haworth p...@lcsql.com wrote: Good point. For lots of reasons, the names of my option menus aren't suitable for display to a user. Maybe the cleanest thing to do then is, if the text of the menu is empty, set its label as suggested by Richard. I like that. Most of the menus in question are under the control of a behavior so this is easy to implement. On Thu, Jul 2, 2015, 8:28 AM Richard Gaskin ambassa...@fourthworld.com wrote: Peter Haworth wrote: So my technique of setting showname to false if the text is empty is the only way round this? Also, you can have a label for an option menu with empty text. Try setting the text of an option menu to empty, then use the message box to set its label to some value. With the OS X HIGs not nearly as complete as they used to be I can no longer find the relevant section on this, but I believe most HIGs suggest that we avoid giving the user the impression the control may be broken by replacing empty items with some explanation of why it's empty, or perhaps a disabled item simply saying None. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.com http://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your
Re: menu buttons and showname
I still can't invisage a situation where you'd want an empty option button. If in Peter's example the first btn was a list of customers, and the second button was a list of their invoices, if a customer has no invoices their name shouldn't appear in the first button. If on the the other hand the first btn is a list of customers and the second btn has the possible options; invoices, email, phone, address which then displays the relevant info in a fld. In this case if the customer has no invoices then that is removed from the choices and Email happens to be the displayed choice; if necessary the user chooses phone or address if that's really what they want - if there is no obvious default choice the it doesn't matter what you choose to display. Again, if the customer had no invoices, no email, no phone and no address what kind of custromer are they?? Either they should NOT appear in the first btn to start with, or the 2nd button choices should change to Enter Email, Enter Phone, Enter Address for any instance where the info doesn't exist so again you wouldn't end up with a button that is empty. An empty btn, even if it's disabled, seems just wrong to me. If it really is empty, set it to invisible. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
Scott Rossi wrote: Often, this type of control has a call to action such as Choose an item, as opposed an indication No selection. It depends on the context of your control. It does, and I wish more Web designers understood that. ;) rant This became popular with form designers where they need to avoid having a default answer, indicating that some action must be taken for a control that requires a value. But over the years I've seen many forms where that lead-in entry is used instead of a having any descriptive label next to it, and often without error-checking to ensure some other value was chosen anyway so they've made it useless in spite of themselves. /rant -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
Often, this type of control has a call to action such as Choose an item, as opposed an indication No selection. It depends on the context of your control. If a selection is required in your set up, the call to action is more communicative. Otherwise, if No selection is a valid selection then that type of message should work. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 7/2/15, 8:47 AM, Peter Haworth p...@lcsql.com wrote: Good point. For lots of reasons, the names of my option menus aren't suitable for display to a user. Maybe the cleanest thing to do then is, if the text of the menu is empty, set its label as suggested by Richard. I like that. Most of the menus in question are under the control of a behavior so this is easy to implement. On Thu, Jul 2, 2015, 8:28 AM Richard Gaskin ambassa...@fourthworld.com wrote: Peter Haworth wrote: So my technique of setting showname to false if the text is empty is the only way round this? Also, you can have a label for an option menu with empty text. Try setting the text of an option menu to empty, then use the message box to set its label to some value. With the OS X HIGs not nearly as complete as they used to be I can no longer find the relevant section on this, but I believe most HIGs suggest that we avoid giving the user the impression the control may be broken by replacing empty items with some explanation of why it's empty, or perhaps a disabled item simply saying None. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
Interesting observation Scott. Makes me wonder if I'm actually using the correct type of menu. For example, I might have an option menu which lists the names of tables in a database and another one that lists the columns in the selected table. There's no call to action in that situation (other than to pick a table and a column), so is an option menu the correct type of control according to HIG? On Thu, Jul 2, 2015 at 10:00 AM Scott Rossi sc...@tactilemedia.com wrote: Often, this type of control has a call to action such as Choose an item, as opposed an indication No selection. It depends on the context of your control. If a selection is required in your set up, the call to action is more communicative. Otherwise, if No selection is a valid selection then that type of message should work. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 7/2/15, 8:47 AM, Peter Haworth p...@lcsql.com wrote: Good point. For lots of reasons, the names of my option menus aren't suitable for display to a user. Maybe the cleanest thing to do then is, if the text of the menu is empty, set its label as suggested by Richard. I like that. Most of the menus in question are under the control of a behavior so this is easy to implement. On Thu, Jul 2, 2015, 8:28 AM Richard Gaskin ambassa...@fourthworld.com wrote: Peter Haworth wrote: So my technique of setting showname to false if the text is empty is the only way round this? Also, you can have a label for an option menu with empty text. Try setting the text of an option menu to empty, then use the message box to set its label to some value. With the OS X HIGs not nearly as complete as they used to be I can no longer find the relevant section on this, but I believe most HIGs suggest that we avoid giving the user the impression the control may be broken by replacing empty items with some explanation of why it's empty, or perhaps a disabled item simply saying None. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
As far as there being a correct type of control, that's open to endless debate. :-) From what you describe, there doesn't seem to be a need for a call to action -- this was suggested simply to address the case that a selection MUST be made for things to work. Since this doesn't seem to be relevant in your situation, I would imagine you'd display a default option as the control label. The bigger issue is why you have an empty option at all. If that's a setting that a user can implement, the option should read something like no selection or empty or similar. If the empty value is something pulled from a table that can't be acted upon, there's no need to include it in the list of options. As always, I may be missing something. :-) Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 7/2/15, 12:59 PM, Peter Haworth p...@lcsql.com wrote: Interesting observation Scott. Makes me wonder if I'm actually using the correct type of menu. For example, I might have an option menu which lists the names of tables in a database and another one that lists the columns in the selected table. There's no call to action in that situation (other than to pick a table and a column), so is an option menu the correct type of control according to HIG? On Thu, Jul 2, 2015 at 10:00 AM Scott Rossi sc...@tactilemedia.com wrote: Often, this type of control has a call to action such as Choose an item, as opposed an indication No selection. It depends on the context of your control. If a selection is required in your set up, the call to action is more communicative. Otherwise, if No selection is a valid selection then that type of message should work. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 7/2/15, 8:47 AM, Peter Haworth p...@lcsql.com wrote: Good point. For lots of reasons, the names of my option menus aren't suitable for display to a user. Maybe the cleanest thing to do then is, if the text of the menu is empty, set its label as suggested by Richard. I like that. Most of the menus in question are under the control of a behavior so this is easy to implement. On Thu, Jul 2, 2015, 8:28 AM Richard Gaskin ambassa...@fourthworld.com wrote: Peter Haworth wrote: So my technique of setting showname to false if the text is empty is the only way round this? Also, you can have a label for an option menu with empty text. Try setting the text of an option menu to empty, then use the message box to set its label to some value. With the OS X HIGs not nearly as complete as they used to be I can no longer find the relevant section on this, but I believe most HIGs suggest that we avoid giving the user the impression the control may be broken by replacing empty items with some explanation of why it's empty, or perhaps a disabled item simply saying None. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.com http://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
What might be handy is some kind of “useTooltipIfEmpty” property. Then the end user would not need to parse the text to eliminate the “call to action” from the real data before working with it, t hen adding the “call to action” back when done. Bob S On Jul 2, 2015, at 08:28 , Richard Gaskin ambassa...@fourthworld.com wrote: Peter Haworth wrote: So my technique of setting showname to false if the text is empty is the only way round this? Also, you can have a label for an option menu with empty text. Try setting the text of an option menu to empty, then use the message box to set its label to some value. With the OS X HIGs not nearly as complete as they used to be I can no longer find the relevant section on this, but I believe most HIGs suggest that we avoid giving the user the impression the control may be broken by replacing empty items with some explanation of why it's empty, or perhaps a disabled item simply saying None. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: menu buttons and showname
Because if you don’t set the label to empty, then the name of the control is displayed as the default choice. It looks like crap, and irritated me, so as a quick fix, I set mine to empty as well. There are times when there is no default choice, that any choice is as viable as the rest. Bob S On Jul 2, 2015, at 13:17 , Scott Rossi sc...@tactilemedia.com wrote: As far as there being a correct type of control, that's open to endless debate. :-) From what you describe, there doesn't seem to be a need for a call to action -- this was suggested simply to address the case that a selection MUST be made for things to work. Since this doesn't seem to be relevant in your situation, I would imagine you'd display a default option as the control label. The bigger issue is why you have an empty option at all. If that's a setting that a user can implement, the option should read something like no selection or empty or similar. If the empty value is something pulled from a table that can't be acted upon, there's no need to include it in the list of options. As always, I may be missing something. :-) Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 7/2/15, 12:59 PM, Peter Haworth p...@lcsql.com wrote: Interesting observation Scott. Makes me wonder if I'm actually using the correct type of menu. For example, I might have an option menu which lists the names of tables in a database and another one that lists the columns in the selected table. There's no call to action in that situation (other than to pick a table and a column), so is an option menu the correct type of control according to HIG? On Thu, Jul 2, 2015 at 10:00 AM Scott Rossi sc...@tactilemedia.com wrote: Often, this type of control has a call to action such as Choose an item, as opposed an indication No selection. It depends on the context of your control. If a selection is required in your set up, the call to action is more communicative. Otherwise, if No selection is a valid selection then that type of message should work. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 7/2/15, 8:47 AM, Peter Haworth p...@lcsql.com wrote: Good point. For lots of reasons, the names of my option menus aren't suitable for display to a user. Maybe the cleanest thing to do then is, if the text of the menu is empty, set its label as suggested by Richard. I like that. Most of the menus in question are under the control of a behavior so this is easy to implement. On Thu, Jul 2, 2015, 8:28 AM Richard Gaskin ambassa...@fourthworld.com wrote: Peter Haworth wrote: So my technique of setting showname to false if the text is empty is the only way round this? Also, you can have a label for an option menu with empty text. Try setting the text of an option menu to empty, then use the message box to set its label to some value. With the OS X HIGs not nearly as complete as they used to be I can no longer find the relevant section on this, but I believe most HIGs suggest that we avoid giving the user the impression the control may be broken by replacing empty items with some explanation of why it's empty, or perhaps a disabled item simply saying None. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.com http://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your
Re: Menu Buttons and the text property
Yes, but that part of the script already works. I have no problem deleting all of the text in the combo box, as I have a special case to account for that. Bob S On Feb 13, 2015, at 17:17 , Randy Hengst iowahen...@mac.com wrote: I'm not at my computer so this idea might just be worthless. Can the first line of your industry list be empty and when you trap for delete go to line 1? On Feb 13, 2015, at 6:43 PM, Bob Sneidar bobsnei...@iotecdigital.com wrote: Thanks for the reply. Let me explain what I am trying to accomplish. I have a combo box with a property containing a list of Industry Names. Things like Retail Services, Auto Repair and such. As the user types, I want to autofill the text with the first choice in that list that matches what the user typed, then select the remaining text after it, so that typing replaces the text after the insertion point. That part works fine. But what happens when the user backspaces? Well it just fills in the remainder of the entry and selects after the insertion point like it normally does. I want the user to be able to delete what is there. Easy enough, I just put empty into the selectedText. But what if there *is* no selected text?? The selectedText is empty, the selected chunk is a description of the first line of the text. So it will delete the whole contents if I use that. Now if the selected chunk behaved in a combo box the way it does in a field, I could parse that and delete the character of the label prior to the insertion point. But it doesn’t, and no commands or functions I’ve found do. I did find a workaround though. The following seems to work properly. It’s a kludge in the finest tradition of epic kludges, but it works. on rawKeyDown pKeyCode if pKeyCode = 65288 then lock messages if the selection is empty then type numToChar(pKeyCode) exit to top end if end if pass rawKeyDown end rawKeyDown on textChanged if the label of me is empty then set the text of me to the options of me exit textChanged end if put the label of me into theValue put length(theValue) into theLength put the Options of me into theOptions filter theOptions with theValue * if theOptions is not empty then set the text of me to theOptions if the text of me is among the lines of theOptions then -- set the label of me to line 1 of theOptions select char theLength +1 to -1 of me end if end if -- focus on me pass textChanged end textChanged ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons and the text property
Trying to come up with a workaround. Turns out that in a combo box the selectedChunk does NOT return the insertion point. Instead it returns the description of the first line of the text of it. For example, I have 5 characters in the combo box, the insertion point is at the end of that text. I have a handler: on backspaceKey put the selectedChunk into StoredChunk end backspaceKey StoredChunk now contains char 1 to 12 of button 1, not char 5 to 4 of button 1 like it should. Instead it's the length of the first line of the text of that button. Again, is this what is supposed to happen, or should I submit a bug report? Bob S On Feb 13, 2015, at 15:37 , Bob Sneidar bobsnei...@iotecdigital.com wrote: Hi all. If I set the text of a Combo Menu to a return delimited list, not only does it change the menu options (as it should) but it also sets the Label to the first line of the menu options! That is undesirable for me. Not sure if this is the intended behavior or not. Presently it is shooting me in the foot. If it is, I’ll find a workaround, otherwise I should file a bug report. Bob S ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons and the text property
Sounds like menuHistory might be helpful. On Feb 13, 2015, at 5:37 PM, Bob Sneidar bobsnei...@iotecdigital.com wrote: Hi all. If I set the text of a Combo Menu to a return delimited list, not only does it change the menu options (as it should) but it also sets the Label to the first line of the menu options! That is undesirable for me. Not sure if this is the intended behavior or not. Presently it is shooting me in the foot. If it is, I’ll find a workaround, otherwise I should file a bug report. Bob S ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons and the text property
Thanks for the reply. Let me explain what I am trying to accomplish. I have a combo box with a property containing a list of Industry Names. Things like Retail Services, Auto Repair and such. As the user types, I want to autofill the text with the first choice in that list that matches what the user typed, then select the remaining text after it, so that typing replaces the text after the insertion point. That part works fine. But what happens when the user backspaces? Well it just fills in the remainder of the entry and selects after the insertion point like it normally does. I want the user to be able to delete what is there. Easy enough, I just put empty into the selectedText. But what if there *is* no selected text?? The selectedText is empty, the selected chunk is a description of the first line of the text. So it will delete the whole contents if I use that. Now if the selected chunk behaved in a combo box the way it does in a field, I could parse that and delete the character of the label prior to the insertion point. But it doesn’t, and no commands or functions I’ve found do. I did find a workaround though. The following seems to work properly. It’s a kludge in the finest tradition of epic kludges, but it works. on rawKeyDown pKeyCode if pKeyCode = 65288 then lock messages if the selection is empty then type numToChar(pKeyCode) exit to top end if end if pass rawKeyDown end rawKeyDown on textChanged if the label of me is empty then set the text of me to the options of me exit textChanged end if put the label of me into theValue put length(theValue) into theLength put the Options of me into theOptions filter theOptions with theValue * if theOptions is not empty then set the text of me to theOptions if the text of me is among the lines of theOptions then -- set the label of me to line 1 of theOptions select char theLength +1 to -1 of me end if end if -- focus on me pass textChanged end textChanged ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons and the text property
I'm not at my computer so this idea might just be worthless. Can the first line of your industry list be empty and when you trap for delete go to line 1? On Feb 13, 2015, at 6:43 PM, Bob Sneidar bobsnei...@iotecdigital.com wrote: Thanks for the reply. Let me explain what I am trying to accomplish. I have a combo box with a property containing a list of Industry Names. Things like Retail Services, Auto Repair and such. As the user types, I want to autofill the text with the first choice in that list that matches what the user typed, then select the remaining text after it, so that typing replaces the text after the insertion point. That part works fine. But what happens when the user backspaces? Well it just fills in the remainder of the entry and selects after the insertion point like it normally does. I want the user to be able to delete what is there. Easy enough, I just put empty into the selectedText. But what if there *is* no selected text?? The selectedText is empty, the selected chunk is a description of the first line of the text. So it will delete the whole contents if I use that. Now if the selected chunk behaved in a combo box the way it does in a field, I could parse that and delete the character of the label prior to the insertion point. But it doesn’t, and no commands or functions I’ve found do. I did find a workaround though. The following seems to work properly. It’s a kludge in the finest tradition of epic kludges, but it works. on rawKeyDown pKeyCode if pKeyCode = 65288 then lock messages if the selection is empty then type numToChar(pKeyCode) exit to top end if end if pass rawKeyDown end rawKeyDown on textChanged if the label of me is empty then set the text of me to the options of me exit textChanged end if put the label of me into theValue put length(theValue) into theLength put the Options of me into theOptions filter theOptions with theValue * if theOptions is not empty then set the text of me to theOptions if the text of me is among the lines of theOptions then -- set the label of me to line 1 of theOptions select char theLength +1 to -1 of me end if end if -- focus on me pass textChanged end textChanged ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
I checked this yesterday with 4.6.1. If I issue menuhistory from the message window to a button with the current choice. menupick does NOT get sent. I know this because I put a breakpoint at the start of the menupick handler in that button and nothing happened. However, if I physically select the same choice that is already selected I DO get a menupick message. Bob On May 10, 2011, at 10:08 PM, Mark Wieder wrote: Pete- Tuesday, May 10, 2011, 8:40:34 PM, you wrote: Hmmm, well I just tried it and got no menuPick when I set the menuHistory to its existing value (running 4.6.0.) Here's the issue: setting the menuHistory of menu buttons would work, but *only* if a new value was being set (not the same as the current value). So the fix was to trigger the menuPick message when the menuHistory command was issued irregardless of the current value of the menu button. That's working now. I just tried it again to make sure, with both pulldown and option menus. script of button 1: on mouseDown set the menuPick of button 3 to 2 end mouseDown script of button 2: on mouseDown set the menuPick of button 4 to 2 end mouseDown script of pulldown button 3: on menuPick pChosen switch pChosen default set the label of me to pChosen answer pChosen end switch end menuPick script of option button 4: on menuPick pChosen switch pChosen default set the label of me to pChosen answer pChosen end switch end menuPick Are you seeing something different? -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Thanks for the input and suggestions, but the set menuhistory .. strategy works to accomplish the task. To deal with the problem of once set-never forget, I set the value to 99 with a second set menuhistory line in my list and had my handler do nothing with the choice was blank. So, any choice can be made and the history set to 99 ready for a new, real choice. Since my goal is to step the user through a visual display of what they would actually see, I want to display that list, make a choice, and then have the action take place rather than just have the action take place -- which the set menuhistory works well for. I still have the problem clicking on the button, displaying the list of options, but then needing a keyboard input rather than a scripted input to go further. There's probably something really simple about it that I'm missing. But, for example, just clicking anywhere in that list which is displayed through a script DOES NOT seem to work for me; actually clicking with a mouse DOES work. Once that list is on the screen, we must wait for something to happen. The controlling script stops. Once you do something (lots of things work), the script chugs along. Best, Dave B. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
That's strange because that's not what I'm seeing - no wonder there's confusion! Here's what I did to test. Put an option menu on a card with the default choices. Put a menuPick handler on the option menu: on menuPIck pitemname answer information pitemname end menuPick Put a button on the same card with a mouseUp script: on mouseUp set the menuHistory of button Option Menu to 2 end mouseUp First time I clicked the button, the answer information dialog appeared with Choice 2 displayed. Second and subsequent times I clicked the button, no answer dialog was displayed. I then changed the button script to set menu history to 1 and the answer information fired with Choice 1 displayed. It appears from other posts that the original problem is solved by using set the menuHistory so I guess this is somewhat academic but it would be good to establish whether this bug really has been fixed and if so, why I don't see the changed behavior, since I rely on that in some of my code. Could it be platform related? I'm running on OSX 10.6.7. Pete Molly's Revenge http://www.mollysrevenge.com On Tue, May 10, 2011 at 10:08 PM, Mark Wieder mwie...@ahsoftware.netwrote: Pete- Tuesday, May 10, 2011, 8:40:34 PM, you wrote: Hmmm, well I just tried it and got no menuPick when I set the menuHistory to its existing value (running 4.6.0.) Here's the issue: setting the menuHistory of menu buttons would work, but *only* if a new value was being set (not the same as the current value). So the fix was to trigger the menuPick message when the menuHistory command was issued irregardless of the current value of the menu button. That's working now. I just tried it again to make sure, with both pulldown and option menus. script of button 1: on mouseDown set the menuPick of button 3 to 2 end mouseDown script of button 2: on mouseDown set the menuPick of button 4 to 2 end mouseDown script of pulldown button 3: on menuPick pChosen switch pChosen default set the label of me to pChosen answer pChosen end switch end menuPick script of option button 4: on menuPick pChosen switch pChosen default set the label of me to pChosen answer pChosen end switch end menuPick Are you seeing something different? -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Well what I do, as I said in a previous post, is I save the last successful choice in a property in the menu. Next time around I get the current selection and compare it to the last choice. If it's the same I exit menuPick. If it's not, then I process the handler, update the property, and pass menuPick. I do that because there is processing later on in the handler that I don't want to repeat. Other people's handlers it may not matter. If it does, this is the way to deal with it no matter which way the selection is made. Bob On May 11, 2011, at 9:44 AM, Pete wrote: That's strange because that's not what I'm seeing - no wonder there's confusion! Here's what I did to test. Put an option menu on a card with the default choices. Put a menuPick handler on the option menu: on menuPIck pitemname answer information pitemname end menuPick Put a button on the same card with a mouseUp script: on mouseUp set the menuHistory of button Option Menu to 2 end mouseUp First time I clicked the button, the answer information dialog appeared with Choice 2 displayed. Second and subsequent times I clicked the button, no answer dialog was displayed. I then changed the button script to set menu history to 1 and the answer information fired with Choice 1 displayed. It appears from other posts that the original problem is solved by using set the menuHistory so I guess this is somewhat academic but it would be good to establish whether this bug really has been fixed and if so, why I don't see the changed behavior, since I rely on that in some of my code. Could it be platform related? I'm running on OSX 10.6.7. Pete Molly's Revenge http://www.mollysrevenge.com On Tue, May 10, 2011 at 10:08 PM, Mark Wieder mwie...@ahsoftware.netwrote: Pete- Tuesday, May 10, 2011, 8:40:34 PM, you wrote: Hmmm, well I just tried it and got no menuPick when I set the menuHistory to its existing value (running 4.6.0.) Here's the issue: setting the menuHistory of menu buttons would work, but *only* if a new value was being set (not the same as the current value). So the fix was to trigger the menuPick message when the menuHistory command was issued irregardless of the current value of the menu button. That's working now. I just tried it again to make sure, with both pulldown and option menus. script of button 1: on mouseDown set the menuPick of button 3 to 2 end mouseDown script of button 2: on mouseDown set the menuPick of button 4 to 2 end mouseDown script of pulldown button 3: on menuPick pChosen switch pChosen default set the label of me to pChosen answer pChosen end switch end menuPick script of option button 4: on menuPick pChosen switch pChosen default set the label of me to pChosen answer pChosen end switch end menuPick Are you seeing something different? -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Yep, I do the same thing, it prevents needless database updating when the value hasn't changed. Just trying to figure out why you and I see the behavior where setting the menuHistory to its existing values does not trigger menuPick but it does for Mark. Pete Molly's Revenge http://www.mollysrevenge.com On Wed, May 11, 2011 at 10:41 AM, Bob Sneidar b...@twft.com wrote: Well what I do, as I said in a previous post, is I save the last successful choice in a property in the menu. Next time around I get the current selection and compare it to the last choice. If it's the same I exit menuPick. If it's not, then I process the handler, update the property, and pass menuPick. I do that because there is processing later on in the handler that I don't want to repeat. Other people's handlers it may not matter. If it does, this is the way to deal with it no matter which way the selection is made. Bob On May 11, 2011, at 9:44 AM, Pete wrote: That's strange because that's not what I'm seeing - no wonder there's confusion! Here's what I did to test. Put an option menu on a card with the default choices. Put a menuPick handler on the option menu: on menuPIck pitemname answer information pitemname end menuPick Put a button on the same card with a mouseUp script: on mouseUp set the menuHistory of button Option Menu to 2 end mouseUp First time I clicked the button, the answer information dialog appeared with Choice 2 displayed. Second and subsequent times I clicked the button, no answer dialog was displayed. I then changed the button script to set menu history to 1 and the answer information fired with Choice 1 displayed. It appears from other posts that the original problem is solved by using set the menuHistory so I guess this is somewhat academic but it would be good to establish whether this bug really has been fixed and if so, why I don't see the changed behavior, since I rely on that in some of my code. Could it be platform related? I'm running on OSX 10.6.7. Pete Molly's Revenge http://www.mollysrevenge.com On Tue, May 10, 2011 at 10:08 PM, Mark Wieder mwie...@ahsoftware.net wrote: Pete- Tuesday, May 10, 2011, 8:40:34 PM, you wrote: Hmmm, well I just tried it and got no menuPick when I set the menuHistory to its existing value (running 4.6.0.) Here's the issue: setting the menuHistory of menu buttons would work, but *only* if a new value was being set (not the same as the current value). So the fix was to trigger the menuPick message when the menuHistory command was issued irregardless of the current value of the menu button. That's working now. I just tried it again to make sure, with both pulldown and option menus. script of button 1: on mouseDown set the menuPick of button 3 to 2 end mouseDown script of button 2: on mouseDown set the menuPick of button 4 to 2 end mouseDown script of pulldown button 3: on menuPick pChosen switch pChosen default set the label of me to pChosen answer pChosen end switch end menuPick script of option button 4: on menuPick pChosen switch pChosen default set the label of me to pChosen answer pChosen end switch end menuPick Are you seeing something different? -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Pete- Wednesday, May 11, 2011, 9:44:31 AM, you wrote: That's strange because that's not what I'm seeing - no wonder there's confusion! Here's what I did to test. Put an option menu on a card with the default choices. I just reopened bug #9301. It's fixed for pulldown and popup menu buttons, but not for option menus. -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Bob- Wednesday, May 11, 2011, 8:30:33 AM, you wrote: I checked this yesterday with 4.6.1. If I issue menuhistory from the message window to a button with the current choice. menupick does NOT get sent. I know this because I put a breakpoint at the start of the menupick handler in that button and nothing happened. However, if I physically select the same choice that is already selected I DO get a menupick message. Bug report has now been reopened. My workaround for option menus is to set the menuHistory to zero, then set the menuHistory to the desired value. -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Ahah! Good shew Sherlock! Bob On May 11, 2011, at 2:49 PM, Mark Wieder wrote: Pete- Wednesday, May 11, 2011, 9:44:31 AM, you wrote: That's strange because that's not what I'm seeing - no wonder there's confusion! Here's what I did to test. Put an option menu on a card with the default choices. I just reopened bug #9301. It's fixed for pulldown and popup menu buttons, but not for option menus. -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Hi Mark, Thanks for the update. I guess it depends on the definition of a bug but to be honest, I think the way this works currently is what I'd expect - no menuPick because nothing new got picked. If processing is needed even though nothing changed, you can send a menuPick message, that way there's flexibility. Of course, I'm definitely biased because I'm relying on the current behavior of menuHistory in some of my code. Pete Molly's Revenge http://www.mollysrevenge.com On Wed, May 11, 2011 at 2:49 PM, Mark Wieder mwie...@ahsoftware.net wrote: Pete- Wednesday, May 11, 2011, 9:44:31 AM, you wrote: That's strange because that's not what I'm seeing - no wonder there's confusion! Here's what I did to test. Put an option menu on a card with the default choices. I just reopened bug #9301. It's fixed for pulldown and popup menu buttons, but not for option menus. -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
To play the bad guy's advocate, why then does it work differently when you select the same thing in an option menu? The *bug* is that the two methods produce different results. But we are straining at gnats here. Bob On May 11, 2011, at 3:26 PM, Pete wrote: Hi Mark, Thanks for the update. I guess it depends on the definition of a bug but to be honest, I think the way this works currently is what I'd expect - no menuPick because nothing new got picked. If processing is needed even though nothing changed, you can send a menuPick message, that way there's flexibility. Of course, I'm definitely biased because I'm relying on the current behavior of menuHistory in some of my code. Pete ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Pete- Wednesday, May 11, 2011, 3:26:28 PM, you wrote: Of course, I'm definitely biased because I'm relying on the current behavior of menuHistory in some of my code. g OTOH, it's easy to check for the current value in the menuPick handler and exit if it's the same. The reason for bug #9301 in the first place was that selecting menuitems from a menubar from a scripted solution wouldn't always work. So on the way to fixing menus, popup and pulldown menus got fixed. Option menus are broken because they now don't act the same as other menu buttons. That's my story and I'm sticking to it. -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Sure, I understand I can check things in menuPick. I guess it comes down to what's the behavior that works most of the time for most people, making that the default, and providing a way to get round the default if it's not what you want. In this very personal sample of one (me), I have yet to come across a situation where I want menupick in an option menu to be triggered if I set the menuhistory to its current value, so it's kind of a pain to have put a workaround for that in every menuPick handler I code. But, you definitely have seniority over me, so I respect your opinion ;-) And I'll just enjoy the way it works now until ti gets changed and then change all mu code to deal with it. Pete Molly's Revenge http://www.mollysrevenge.com On Wed, May 11, 2011 at 6:39 PM, Mark Wieder mwie...@ahsoftware.net wrote: Pete- Wednesday, May 11, 2011, 3:26:28 PM, you wrote: Of course, I'm definitely biased because I'm relying on the current behavior of menuHistory in some of my code. g OTOH, it's easy to check for the current value in the menuPick handler and exit if it's the same. The reason for bug #9301 in the first place was that selecting menuitems from a menubar from a scripted solution wouldn't always work. So on the way to fixing menus, popup and pulldown menus got fixed. Option menus are broken because they now don't act the same as other menu buttons. That's my story and I'm sticking to it. -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Bonjour David, Did you try : set the menuHistory of btn examples to 1 -- (or 2, 3, etc) Best regards from Grenoble André Le 9 mai 2011 à 23:18, David Brooks a écrit : I DO exactly those sorts of things. But, when I send a menupick message, nothing happens. I've tried things like: send menupick (line 3 of btn Examples) to btn Examples and send menupick aspirin to btn Examples However, I've never used the term combo box and it looks as if I have a new avenue to try. Many thanks. This looks to be similar to what one would do with a field. MANY thanks. Best, Dave B. On May 9, 2011, at 2:16 PM, dunb...@aol.com wrote: When you say you want to drive the menuItems displayed by script, does that mean you never want to use the mouse at all? I made a workaround recently where I did something like this, and I am giving you a snippet for your examination. Make two buttons, one an ordinary one, and one a combo box. Put several choices into the combo. Place the comboBox so that the loc of its selection arrow is, say, 200,200. In the regular button script write: on mouseUp click at 200,200 wait 50 click at 175, 225 + random(100) end mouseUp This should open the combo box and select a random line within it. You can trap a menuPick message inside the combo box. Not sure what you are doing, but this might give you a hint as to a possible method. HTH. Craig Newman -Original Message- From: David Brooks dbro...@unlserve.unl.edu To: How to use LiveCode use-livecode@lists.runrev.com Sent: Mon, May 9, 2011 2:14 pm Subject: Menu Buttons I am trying to create a series of helps where I step a user through a process using the underlying tool. I have one help field that variously shows, hides, fills, and moves around. The scripts say things (aural feedback). There is a pointer button that locates as needed, flashes, and shows/hides. Here's my problem. Suppose I have a menu button that affords several choices. In my application, I can click the button, move among the choices from a list that is displayed -- with a choice automatically hiliting as I move around (hovering) in the list, and then click to make the hilited choice. I want to drive that from a script. Is there an easy way? The list seems to behave like some sort of modal stack that I must deal with. That is, if I create a script that pops out the list, that list behaves as I would expect -- FROM MOUSE ACTIONS -- but I haven't found scripting that leads to the same effects. I suppose I could capture images and use these AS IF they were the real thing, but then I'd have less flexibility than if I did this from scripts. Should I simply redesign things such that buttons display fields and try to go from there? I seem to be able to get that approach to work from scripts, but it seems cumbersome. Thanks in advance for your help. Dave B. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Or try: select menuItem 1 of menu File -- Tom McGrath III http://lazyriver.on-rev.com 3mcgr...@comcast.net On May 9, 2011, at 10:05 PM, Mark Wieder wrote: David- Monday, May 9, 2011, 2:18:41 PM, you wrote: I've tried things like: send menupick (line 3 of btn Examples) to btn Examples and send menupick aspirin to btn Examples Try setting the menuHistory of the button -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
I might be wrong but I think the send commands, as you listed them, aren't correct - I believe the message and it's parameters have to be one string. So something like: send menuPick aspirin to button Examples or send menuPick (line 3 of btn Examples) to btn Examples Pete Molly's Revenge http://www.mollysrevenge.com On Tue, May 10, 2011 at 3:02 AM, André Bisseret andre.bisse...@wanadoo.frwrote: Bonjour David, Did you try : set the menuHistory of btn examples to 1 -- (or 2, 3, etc) Best regards from Grenoble André Le 9 mai 2011 à 23:18, David Brooks a écrit : I DO exactly those sorts of things. But, when I send a menupick message, nothing happens. I've tried things like: send menupick (line 3 of btn Examples) to btn Examples and send menupick aspirin to btn Examples However, I've never used the term combo box and it looks as if I have a new avenue to try. Many thanks. This looks to be similar to what one would do with a field. MANY thanks. Best, Dave B. On May 9, 2011, at 2:16 PM, dunb...@aol.com wrote: When you say you want to drive the menuItems displayed by script, does that mean you never want to use the mouse at all? I made a workaround recently where I did something like this, and I am giving you a snippet for your examination. Make two buttons, one an ordinary one, and one a combo box. Put several choices into the combo. Place the comboBox so that the loc of its selection arrow is, say, 200,200. In the regular button script write: on mouseUp click at 200,200 wait 50 click at 175, 225 + random(100) end mouseUp This should open the combo box and select a random line within it. You can trap a menuPick message inside the combo box. Not sure what you are doing, but this might give you a hint as to a possible method. HTH. Craig Newman -Original Message- From: David Brooks dbro...@unlserve.unl.edu To: How to use LiveCode use-livecode@lists.runrev.com Sent: Mon, May 9, 2011 2:14 pm Subject: Menu Buttons I am trying to create a series of helps where I step a user through a process using the underlying tool. I have one help field that variously shows, hides, fills, and moves around. The scripts say things (aural feedback). There is a pointer button that locates as needed, flashes, and shows/hides. Here's my problem. Suppose I have a menu button that affords several choices. In my application, I can click the button, move among the choices from a list that is displayed -- with a choice automatically hiliting as I move around (hovering) in the list, and then click to make the hilited choice. I want to drive that from a script. Is there an easy way? The list seems to behave like some sort of modal stack that I must deal with. That is, if I create a script that pops out the list, that list behaves as I would expect -- FROM MOUSE ACTIONS -- but I haven't found scripting that leads to the same effects. I suppose I could capture images and use these AS IF they were the real thing, but then I'd have less flexibility than if I did this from scripts. Should I simply redesign things such that buttons display fields and try to go from there? I seem to be able to get that approach to work from scripts, but it seems cumbersome. Thanks in advance for your help. Dave B. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
If it's a menu that can change programmatically (like a list of departments for example) then get the text of the field, get the lineoffset of what you are looking for, then set the menuhistory to that. For extra credit, save the last pick in a property, then check to see if the user selected the same thing next time around, and bail if he did to avoid any unwanted processing. Setting the menuhistory WILL trigger menupick. That's where you do it all. Remember to pass menupick in your menupick handler if you don't bail! Bob On May 9, 2011, at 7:05 PM, Mark Wieder wrote: David- Monday, May 9, 2011, 2:18:41 PM, you wrote: I've tried things like: send menupick (line 3 of btn Examples) to btn Examples and send menupick aspirin to btn Examples Try setting the menuHistory of the button -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
or dispatch menupick to button Examples with Aspirin Bob On May 10, 2011, at 9:43 AM, Pete wrote: I might be wrong but I think the send commands, as you listed them, aren't correct - I believe the message and it's parameters have to be one string. So something like: send menuPick aspirin to button Examples or send menuPick (line 3 of btn Examples) to btn Examples Pete Molly's Revenge http://www.mollysrevenge.com On Tue, May 10, 2011 at 3:02 AM, André Bisseret andre.bisse...@wanadoo.frwrote: Bonjour David, Did you try : set the menuHistory of btn examples to 1 -- (or 2, 3, etc) Best regards from Grenoble André Le 9 mai 2011 à 23:18, David Brooks a écrit : I DO exactly those sorts of things. But, when I send a menupick message, nothing happens. I've tried things like: send menupick (line 3 of btn Examples) to btn Examples and send menupick aspirin to btn Examples However, I've never used the term combo box and it looks as if I have a new avenue to try. Many thanks. This looks to be similar to what one would do with a field. MANY thanks. Best, Dave B. On May 9, 2011, at 2:16 PM, dunb...@aol.com wrote: When you say you want to drive the menuItems displayed by script, does that mean you never want to use the mouse at all? I made a workaround recently where I did something like this, and I am giving you a snippet for your examination. Make two buttons, one an ordinary one, and one a combo box. Put several choices into the combo. Place the comboBox so that the loc of its selection arrow is, say, 200,200. In the regular button script write: on mouseUp click at 200,200 wait 50 click at 175, 225 + random(100) end mouseUp This should open the combo box and select a random line within it. You can trap a menuPick message inside the combo box. Not sure what you are doing, but this might give you a hint as to a possible method. HTH. Craig Newman -Original Message- From: David Brooks dbro...@unlserve.unl.edu To: How to use LiveCode use-livecode@lists.runrev.com Sent: Mon, May 9, 2011 2:14 pm Subject: Menu Buttons I am trying to create a series of helps where I step a user through a process using the underlying tool. I have one help field that variously shows, hides, fills, and moves around. The scripts say things (aural feedback). There is a pointer button that locates as needed, flashes, and shows/hides. Here's my problem. Suppose I have a menu button that affords several choices. In my application, I can click the button, move among the choices from a list that is displayed -- with a choice automatically hiliting as I move around (hovering) in the list, and then click to make the hilited choice. I want to drive that from a script. Is there an easy way? The list seems to behave like some sort of modal stack that I must deal with. That is, if I create a script that pops out the list, that list behaves as I would expect -- FROM MOUSE ACTIONS -- but I haven't found scripting that leads to the same effects. I suppose I could capture images and use these AS IF they were the real thing, but then I'd have less flexibility than if I did this from scripts. Should I simply redesign things such that buttons display fields and try to go from there? I seem to be able to get that approach to work from scripts, but it seems cumbersome. Thanks in advance for your help. Dave B. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
Re: Menu Buttons
On May 10, 2011, at 9:43 AM, Pete wrote:
I might be wrong but I think the send commands, as you listed them,
aren't
correct - I believe the message and it's parameters have to be one
string.
So something like:
send menuPick aspirin to button Examples
or
send menuPick (line 3 of btn Examples) to btn Examples
Pete, you are probably correct 'most of the time' and the reason is
that most of the time the interpreter will use what it thinks you mean
when it finds ambiguous syntax, and get it right.
What this means is that to the interpreter...
send menuPick (line 3 of btn Examples) to btn Examples
could mean menuPick as a reserved word
could mean menuPick as a variable
or
could mean menuPick as a string
Hopefully you can see that you are leaving it up to the interpreter to
know which you intend.
send desiredKeyword paramVariable to btn Examples
-- can vary depending on what the interpreter sees as
-- desiredKeyword {literal string, variable, reserved word}
If it is seen as a reserved word, then it probably evaluates as an
empty string.
step 2 If it is seen as a variable container, then it evaluates the
value of that variable.
and step 3 in the decision tree is to assume it is a literal string.
To be consistent and reliable, a programmer should always insure a
literal string is used and arrives as the exact equivalent desired,
including spaces and commas.
Hope this helps.
Jim Ault
Las Vegas
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Oh hey didn't know that. It is true however, that selecting the current menu selection DOES trigger a menupick, which is probably why I thought setting the menuhistory to what it already is did the same thing. Bob On May 10, 2011, at 11:15 AM, Pete wrote: I think it's also worth commenting on setting the menuHistory to solve this problem. If a handler sets the menuHistory to it's existing value, no menuPick message is generated. I can't tell if that's significant to this problem but good to be aware of. Pete Molly's Revenge http://www.mollysrevenge.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Pete- Tuesday, May 10, 2011, 11:15:38 AM, you wrote: I think it's also worth commenting on setting the menuHistory to solve this problem. If a handler sets the menuHistory to it's existing value, no menuPick message is generated. I can't tell if that's significant to this problem but good to be aware of. That's a bug (#9301) that got fixed in the 4.6.0 release. -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Hmmm, well I just tried it and got no menuPick when I set the menuHistory to its existing value (running 4.6.0.) I read the text of the bug report and it's a little confusing about what actually got fixed or even if anything did. My reply was strictly to do with option menus but the bug report seems to be referring to pulldown/popup/cascade menus, although even then, I'm not sure what got fixed. So I stand by my original comment about this, at least as far as option menus are concerned. And if indeed it did change and I'm somehow not experiencing the change, then it would be great if the user comment in the dictionary was either updated or deleted. Molly's Revenge http://www.mollysrevenge.com On Tue, May 10, 2011 at 5:51 PM, Mark Wieder mwie...@ahsoftware.net wrote: Pete- Tuesday, May 10, 2011, 11:15:38 AM, you wrote: I think it's also worth commenting on setting the menuHistory to solve this problem. If a handler sets the menuHistory to it's existing value, no menuPick message is generated. I can't tell if that's significant to this problem but good to be aware of. That's a bug (#9301) that got fixed in the 4.6.0 release. -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
Pete- Tuesday, May 10, 2011, 8:40:34 PM, you wrote: Hmmm, well I just tried it and got no menuPick when I set the menuHistory to its existing value (running 4.6.0.) Here's the issue: setting the menuHistory of menu buttons would work, but *only* if a new value was being set (not the same as the current value). So the fix was to trigger the menuPick message when the menuHistory command was issued irregardless of the current value of the menu button. That's working now. I just tried it again to make sure, with both pulldown and option menus. script of button 1: on mouseDown set the menuPick of button 3 to 2 end mouseDown script of button 2: on mouseDown set the menuPick of button 4 to 2 end mouseDown script of pulldown button 3: on menuPick pChosen switch pChosen default set the label of me to pChosen answer pChosen end switch end menuPick script of option button 4: on menuPick pChosen switch pChosen default set the label of me to pChosen answer pChosen end switch end menuPick Are you seeing something different? -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
When you say you want to drive the menuItems displayed by script, does that mean you never want to use the mouse at all? I made a workaround recently where I did something like this, and I am giving you a snippet for your examination. Make two buttons, one an ordinary one, and one a combo box. Put several choices into the combo. Place the comboBox so that the loc of its selection arrow is, say, 200,200. In the regular button script write: on mouseUp click at 200,200 wait 50 click at 175, 225 + random(100) end mouseUp This should open the combo box and select a random line within it. You can trap a menuPick message inside the combo box. Not sure what you are doing, but this might give you a hint as to a possible method. HTH. Craig Newman -Original Message- From: David Brooks dbro...@unlserve.unl.edu To: How to use LiveCode use-livecode@lists.runrev.com Sent: Mon, May 9, 2011 2:14 pm Subject: Menu Buttons I am trying to create a series of helps where I step a user through a process using the underlying tool. I have one help field that variously shows, hides, fills, and moves around. The scripts say things (aural feedback). There is a pointer button that locates as needed, flashes, and shows/hides. Here's my problem. Suppose I have a menu button that affords several choices. In my application, I can click the button, move among the choices from a list that is displayed -- with a choice automatically hiliting as I move around (hovering) in the list, and then click to make the hilited choice. I want to drive that from a script. Is there an easy way? The list seems to behave like some sort of modal stack that I must deal with. That is, if I create a script that pops out the list, that list behaves as I would expect -- FROM MOUSE ACTIONS -- but I haven't found scripting that leads to the same effects. I suppose I could capture images and use these AS IF they were the real thing, but then I'd have less flexibility than if I did this from scripts. Should I simply redesign things such that buttons display fields and try to go from there? I seem to be able to get that approach to work from scripts, but it seems cumbersome. Thanks in advance for your help. Dave B. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
I DO exactly those sorts of things. But, when I send a menupick message, nothing happens. I've tried things like: send menupick (line 3 of btn Examples) to btn Examples and send menupick aspirin to btn Examples However, I've never used the term combo box and it looks as if I have a new avenue to try. Many thanks. This looks to be similar to what one would do with a field. MANY thanks. Best, Dave B. On May 9, 2011, at 2:16 PM, dunb...@aol.com wrote: When you say you want to drive the menuItems displayed by script, does that mean you never want to use the mouse at all? I made a workaround recently where I did something like this, and I am giving you a snippet for your examination. Make two buttons, one an ordinary one, and one a combo box. Put several choices into the combo. Place the comboBox so that the loc of its selection arrow is, say, 200,200. In the regular button script write: on mouseUp click at 200,200 wait 50 click at 175, 225 + random(100) end mouseUp This should open the combo box and select a random line within it. You can trap a menuPick message inside the combo box. Not sure what you are doing, but this might give you a hint as to a possible method. HTH. Craig Newman -Original Message- From: David Brooks dbro...@unlserve.unl.edu To: How to use LiveCode use-livecode@lists.runrev.com Sent: Mon, May 9, 2011 2:14 pm Subject: Menu Buttons I am trying to create a series of helps where I step a user through a process using the underlying tool. I have one help field that variously shows, hides, fills, and moves around. The scripts say things (aural feedback). There is a pointer button that locates as needed, flashes, and shows/hides. Here's my problem. Suppose I have a menu button that affords several choices. In my application, I can click the button, move among the choices from a list that is displayed -- with a choice automatically hiliting as I move around (hovering) in the list, and then click to make the hilited choice. I want to drive that from a script. Is there an easy way? The list seems to behave like some sort of modal stack that I must deal with. That is, if I create a script that pops out the list, that list behaves as I would expect -- FROM MOUSE ACTIONS -- but I haven't found scripting that leads to the same effects. I suppose I could capture images and use these AS IF they were the real thing, but then I'd have less flexibility than if I did this from scripts. Should I simply redesign things such that buttons display fields and try to go from there? I seem to be able to get that approach to work from scripts, but it seems cumbersome. Thanks in advance for your help. Dave B. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
I think you may need to structure the send statement differently: put menupick line 3 of btn Examples into myCommand send myCommand to btn Examples send menupick aspirin to btn Examples Pete Molly's Revenge http://www.mollysrevenge.com On Mon, May 9, 2011 at 2:18 PM, David Brooks dbro...@unlserve.unl.eduwrote: I DO exactly those sorts of things. But, when I send a menupick message, nothing happens. I've tried things like: send menupick (line 3 of btn Examples) to btn Examples and send menupick aspirin to btn Examples However, I've never used the term combo box and it looks as if I have a new avenue to try. Many thanks. This looks to be similar to what one would do with a field. MANY thanks. Best, Dave B. On May 9, 2011, at 2:16 PM, dunb...@aol.com wrote: When you say you want to drive the menuItems displayed by script, does that mean you never want to use the mouse at all? I made a workaround recently where I did something like this, and I am giving you a snippet for your examination. Make two buttons, one an ordinary one, and one a combo box. Put several choices into the combo. Place the comboBox so that the loc of its selection arrow is, say, 200,200. In the regular button script write: on mouseUp click at 200,200 wait 50 click at 175, 225 + random(100) end mouseUp This should open the combo box and select a random line within it. You can trap a menuPick message inside the combo box. Not sure what you are doing, but this might give you a hint as to a possible method. HTH. Craig Newman -Original Message- From: David Brooks dbro...@unlserve.unl.edu To: How to use LiveCode use-livecode@lists.runrev.com Sent: Mon, May 9, 2011 2:14 pm Subject: Menu Buttons I am trying to create a series of helps where I step a user through a process using the underlying tool. I have one help field that variously shows, hides, fills, and moves around. The scripts say things (aural feedback). There is a pointer button that locates as needed, flashes, and shows/hides. Here's my problem. Suppose I have a menu button that affords several choices. In my application, I can click the button, move among the choices from a list that is displayed -- with a choice automatically hiliting as I move around (hovering) in the list, and then click to make the hilited choice. I want to drive that from a script. Is there an easy way? The list seems to behave like some sort of modal stack that I must deal with. That is, if I create a script that pops out the list, that list behaves as I would expect -- FROM MOUSE ACTIONS -- but I haven't found scripting that leads to the same effects. I suppose I could capture images and use these AS IF they were the real thing, but then I'd have less flexibility than if I did this from scripts. Should I simply redesign things such that buttons display fields and try to go from there? I seem to be able to get that approach to work from scripts, but it seems cumbersome. Thanks in advance for your help. Dave B. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Menu Buttons
David- Monday, May 9, 2011, 2:18:41 PM, you wrote: I've tried things like: send menupick (line 3 of btn Examples) to btn Examples and send menupick aspirin to btn Examples Try setting the menuHistory of the button -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
