You are correct. Essentially, any menu that offers a list of strings to display
on the menu button itself cannot use submenus. It makes sense really. I’ve
never seen an option menu in any other application that allows a submenu
choice.
Bob S
> On May 31, 2024, at 6:23 AM, Craig Newman via us
Hi.
I believe that only pullDown and popUp menu styles can support submenus. Combo
boxes and Option menus styles do not.
Craig
> On May 31, 2024, at 5:32 AM, jbv via use-livecode
> wrote:
>
> Hi list,
>
> I am trying to create a hierarchical submenu in an option menu button
> with LC 9.6.
>
Hi list,
I am trying to create a hierarchical submenu in an option menu button
with LC 9.6.
I have found this solution that seems to work only with pulldown buttons
:
https://use-livecode.runrev.narkive.com/cBfAjix2/cascading-menu
I also found this LC lesson that suggests to use polylists :
ht
Some have indicated they like to have a development menu in their projects that
they remove when compiling to standalone. A better way is to simply hide the
development menu then call this handler:
on arrangeMenus tMenu
-- rearranges the menus based upon their order ignoring invisible menu
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. Wo
Hi Bob:
I would propose that empty is not an informative value for a user.
Something like "" 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" wrote:
>
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 wrote:
>
> “Set the label of button myBtn to space” makes an option button appear blank
> but does not interfere with a user’s
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
mailto:lan.kc.macm...@gmail.com>> 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
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
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
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 Gaski
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
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 rele
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
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. ;)
This became popular with form designers where they
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 the
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 thi
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
Yep, that's one of the things I've done.
On Thu, Jul 2, 2015, 7:54 AM Randy Hengst 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 H
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 wrote:
>
> No, I s
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. L
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 wrote:
> Peter,
>
> I agree with the other here that the beh
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
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
taking the
> place of the actual name.
>
>
> What am I missing?
>
>
> Craig
>
>
>
> -Original Message-
> From: Peter Haworth
> To: How to use LiveCode
> Sent: Wed, Jul 1, 2015 9:52 pm
> Subject: menu buttons and showname
>
>
> I've
ordinary button, where if the label is not empty,
then that label is shown as the "name" of the button, taking the place of the
actual name.
What am I missing?
Craig
-Original Message-
From: Peter Haworth
To: How to use LiveCode
Sent: Wed, Jul 1, 2015 9:52 pm
Sub
I've struggled with using the showName property of a menu button pretty
much ever since I started using LC and beginning to wonder if I'm missing
something.
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 -
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 wrote:
>
> I'm not at my computer so this idea might just be worthless. Can the first
>
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 wrote:
>
> Thanks for the reply. Let me explain what I am trying to accomplish.
>
> I have a com
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
Sounds like menuHistory might be helpful.
> On Feb 13, 2015, at 5:37 PM, Bob Sneidar 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 opti
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
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 shootin
OK, might still be able to try it, just got a Windows box for testing.
Pete
On Thu, Jan 26, 2012 at 10:08 AM, Mark Schonewille <
m.schonewi...@economy-x-talk.com> wrote:
> He Pete, we're talking Windows here.
>
> --
> Best regards,
>
> Mark Schonewille
>
> Economy-x-Talk Consulting and Software E
He Pete, we're talking Windows here.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553
Download the Installer Maker Plugin 1.7 for LiveCode here http://qery.us/za
On
Hi Mark,
Option menus don't have scrollbars do they? At least not on OS X) Do you
mean comboboxes? If so, all works fine for me (on OS X).
Pete
On Thu, Jan 26, 2012 at 9:37 AM, Mark Schonewille <
m.schonewi...@economy-x-talk.com> wrote:
> Hi,
>
> I just got a complaint about non-functional scro
Hi Guglielmo,
I tested it with a new stack on XP and got the same results. Therefore, I'm now
asking for confirmation on the list.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogramme
Because is my complaint ...
... I want just to add that this happen with the 'Installer Maker
Plugin', on the language selection menu, on Win 7 64 bit and *NOT *on OS
X, both running LiveCode 5.0.2
Regards,
Guglielmo
On 26.01.2012 18:37, Mark Schonewille wrote:
Hi,
I just got a complaint a
Hi,
I just got a complaint about non-functional scrollbars of option menus. If the
menuLines < number of lines of the text then a scrollbar appears but it is
impossible to scroll. Does anyone else see this?
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
H
he 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
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
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
day, 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
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
>
>
> __
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 but
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
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 >wrote:
> >
> >>
d 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 wrote:
>
>> Pete-
>>
>> Tuesday, May 10, 2011, 8
On Tue, 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:
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,
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 issue
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
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 se
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 go
I think that menuHistory behavior is what you'd want most of the time but
just good to make people aware of it, just in case. And yes, selecting the
current selection does trigger a menuPick so that's the way to do get around
the menuHistory behavior if it matters. But then, as you pointed out, y
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
The original code examples didn't have the && between menuPick and (line 3
of btn "Examples") - that was the real problem I saw, probably should have
made that clearer. Personally, I've got into the habit of using dispatch
rather than send whenever possible just because the syntax lends itself to
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 b
et 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:
>>>>
&
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
t; 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
>
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
p; 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 p
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
. 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
> >
> >
> >
> >
> >
> >
> > -O
s 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
>
>
>
>
>
>
LiveCode
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"
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 sh
69 matches
Mail list logo