LiveCode Forums.

Hi,

I have a Pulldown menu on a card that is used to display numbers between "-5" and "+5", however the negative values don't show up in the list, I only get as best I can describe them as "lines" where the numbers should be. How can I fix this?

jpottsx1 wrote: I have a Pulldown menu on a card that is used to display numbers between "-5" and "+5", however the negative values don't show up in the list, I only get as best I can describe them as "lines" where the numbers should be. How can I fix this?

That's a nice one (bug ?).

Solution : add a space before, on each line.

I just made a pulldown button with that range and it seems to display okay.

How did you create that menu?

Richard,

this is a bug and I already reported this a couple of years ago

The only workaround is to add a SPACE before each MINUS sign as bangkok already mentioned!


Best

Klaus

I don't doubt your bug report, but yet I was able to create a pulldown menu with the items described so it seems that either I misunderstood the request or the problem may be limited to the LC IDE and not necessarily the engine (I built my functional test menu in MC).

I'll be happy to review the details in the report - what is the RQCC number?

Hi Richard,

I just did a quick check in MetaCard, no way, see screenshot.
I put this into the "pulldown" menu button:
1
2
3
4
5
-1
-2
-3
-4
-5

I saw that this was an enhacement request so I changed this to "normal bug":
http://quality.runrev.com/show_bug.cgi?id=5822


Best

Klaus

Thanks for the screen shot - that was the key: I had thought this affected all platforms, but it doesn't seem a problem on Mac OS X (updated the RQCC report accordingly).

Richard,

the screenshot IS from OS X!

But this only affects "pulldown" menu buttons, "popup" etc. work fine!


Best

Klaus

Hi,
and
no spaces, just what it shows. MacOSX 10.6.8, LC 4.6.3

???

Kind regards

Bernd

Klaus wrote:Richard,

the screenshot IS from OS X!

I've found the difference: when left to the engine's defaults, the menu button's border property is set to 2, and the button will use the OS routines to draw the menu, which draws them appropriately. But if you set the button's border to 0, the internal engine routines are used to draw the menus as they are for all menus on Win and Linux, which exhibits the erroneous behavior reported.

I'm running Windows 7 and have updated to the latest LC release and I still get the erroneous lines in my menu whether I have my border set to zero or not, and enabling the the border or not still produces the same results.

My assumption is that this error is caused by the menu system's default programming that allows a "-" to produce a menu divider when creating a menu based resource. When using the menu builder a dash/"-" inserts a menu item divider. The code must be shared with the button menu items.

That the issue is consistent on Windows in spite of the borderwidth setting is to be expected; the "fix" of setting the borderwidth to 2 invokes correct behaviors only by relying on OS X's menu routines when running on that OS.

Hi Richard,

could you please add some comments to the Qualtiy Center?
I think this NEEDS some explanation, due to the different results here on OS X, thanks!


Best

Klaus

Good idea - done.

Did anyone try escaping the hyphen? I.e.: \-