Xojo Conferences
MBSOct2019CologneDE

4.5 MenuItem Bug? (Real Studio network user group Mailinglist archive)

Back to the thread list
Previous thread: Editfield Problem
Next thread: Sonnet G3 Upgrade Card & REALbasic


Localized strings in tabpanel   -   Jan Erik Moström <
  4.5 MenuItem Bug?   -   katk attbi.com
   Re: 4.5 MenuItem Bug?   -   Dennis Birch
    4.5 MenuItem Bug?   -   katk attbi.com

4.5 MenuItem Bug?
Date: 31.05.02 22:33 (Fri, 31 May 2002 21:33:41 +0000)
From: katk attbi.com
I just discovered something which is a major pain for me,
and I hope others agree its a bug... What do you think?

If you set a menuitem in the IDE to have sub-items (it is
a parent) then in code set Item.Visible = false and later
set it back to true that item is no longer heriarchical.

I found this because I have an app I developing with
potentally many different types of windows and I was bount
tp put all the unique to a window functionality in one
Menu...

To do this flexibly and support submenus within that menu
I cludged together something wich should have worked
IMO...

I made a bunch of generic menuitem arrays (9) where i
changed the text of items and created clones of items and
subitems as necessary (initally each 0th index parent item
has one 0th idex subitem) making unused Index = 0 ones
invisible and closing extra ones with index > 0. The
invisiblity is important because of teh wind variety of
possible items and the varing numbers.

I also took advantage of the fact that clones of
heierachial menuItems were not heirarchical (which mahes
sense as there is no way to associate a sunitem with a
parent

This should have given me fexability in mixing nornal
and single sublevel heirarchical menu items in almost any
order... But i got tripped up by the loss of
"heirarchiality"

To illustrate in a much simpler situation:

Make a new project

Add a menu called test and a herachical menu item called
testitem1

Create a new cals with application as super.

in the open event set testitem1.Visible = false

In the default Window put a button with this in the action
event:
testitem1.Visible = NOT testitem1.Visible

Run the app and see what happens.

- karen

---
Subscribe to the digest:
<mailto:<email address removed>>
Unsubscribe:
<mailto:<email address removed>>

Re: 4.5 MenuItem Bug?
Date: 31.05.02 22:40 (Fri, 31 May 2002 14:40:52 -0700)
From: Dennis Birch
It's a longstanding bug, going back at least to version 2.1 if I
remember correctly. I REALbugged it long ago and frankly gave up hope
of it ever being fixed.

At 9:33 PM +0000 5/31/02, <email address removed> wrote:
>I just discovered something which is a major pain for me,
>and I hope others agree its a bug... What do you think?

---
Subscribe to the digest:
<mailto:<email address removed>>
Unsubscribe:
<mailto:<email address removed>>

4.5 MenuItem Bug?
Date: 31.05.02 23:42 (Fri, 31 May 2002 22:42:48 +0000)
From: katk attbi.com
I just discovered something which is a major pain for me,
and I hope others agree its a bug... What do you think?

If you set a menuitem in the IDE to have sub-items (it is
a parent) then in code set Item.Visible = false and later
set it back to true that item is no longer heriarchical.

I found this because I have an app I developing with
potentally many different types of windows and I was bount
tp put all the unique to a window functionality in one
Menu...

To do this flexibly and support submenus within that menu
I cludged together something wich should have worked
IMO...

I made a bunch of generic menuitem arrays (9) where i
changed the text of items and created clones of items and
subitems as necessary (initally each 0th index parent item
has one 0th idex subitem) making unused Index = 0 ones
invisible and closing extra ones with index > 0. The
invisiblity is important because of teh wind variety of
possible items and the varing numbers.

I also took advantage of the fact that clones of
heierachial menuItems were not heirarchical (which mahes
sense as there is no way to associate a sunitem with a
parent

This should have given me fexability in mixing nornal
and single sublevel heirarchical menu items in almost any
order... But i got tripped up by the loss of
"heirarchiality"

To illustrate in a much simpler situation:

Make a new project

Add a menu called test and a herachical menu item called
testitem1

Create a new cals with application as super.

in the open event set testitem1.Visible = false

In the default Window put a button with this in the action
event:
testitem1.Visible = NOT testitem1.Visible

Run the app and see what happens.

- karen

---
Subscribe to the digest:
<mailto:<email address removed>>
Unsubscribe:
<mailto:<email address removed>>