Re: Opinion wanted
- From: "Michael C" <nospam@xxxxxxxxxx>
- Date: Tue, 13 Mar 2007 14:06:24 +1100
"Jack White" <no_spam@xxxxxxxxxxx> wrote in message
news:exvixbMYHHA.4552@xxxxxxxxxxxxxxxxxxxxxxx
I was really looking for a mechanical solution on how to handle this in
.NET (if a mainstream way does in fact exist). I need to prevent users
from selecting certain menu items for instance whenever the current
control in my form is invalid. Simply disabling it until the control is
valid again doesn't cut it since users may become confused as to why it's
suddenly unavailable. The thread is now off-topic however.
If you really want to go with your approach then you could do something like
I did in visual basic 6 to implement security for my menus. I created a
wrapper collection for the menus. When the app started this collection was
populated by passing in a reference to each menu item. Additional
information could be passed into the collection to be associated with each
menu item. I could then iterate through the collection and hide/disable
different menu items based on these flags. You could have a flag to indicate
that the menu should be disabled during user input. If you don't want to
disable the menu the you could check this flag in the menu's click event.
This is starting to get complicated though for no real benefit to the user,
in fact it is a hassle to the user because if they are selecting that menu
they wanted to go to that menu for a reason. More than likely the very
reason is because of the error.
Michael
.
- References:
- Re: Opinion wanted
- From: Otis Mukinfus
- Re: Opinion wanted
- From: Jack White
- Re: Opinion wanted
- From: md
- Re: Opinion wanted
- From: Jack White
- Re: Opinion wanted
- Prev by Date: Re: Opinion wanted
- Next by Date: Re: Passing values from child to parent form
- Previous by thread: Re: Opinion wanted
- Next by thread: OutOfMemoryException
- Index(es):
Relevant Pages
|