M
MDB
This may sound like a naive question, but that's only because I'm naive
about most things ASP.NET, as my background is primarily Lotus Notes
Development, and before that, DOS-based FoxPro.
Is there a way to group elements, such as a set of textboxes and related
labels, in effect giving them a common group name that could then be used to
disable/enable other elements on the page? For example if I have a
_textChanged event on a textbox that detects an error, it would be lovely to
be able to hide all the other controls on the page, to reinforce the notion
that the user really can't do anything until they fix the error in the
original textbox. I've dealt too often with users who need to be hit over
the head with a sledgehammer like that.
Right now, I see my choices as: 1) putting the controls to be hidden in a
panel and hiding the panel, which is not an ideal solution because it would
involved redesigning the screen; or 2) immediately redirect the user out of
the edit screen back to the main screen, and display a bright red error msg
in my lblErrMsg label telling them what they just did wrong. Both accomplish
the goal of keeping the user from doing anything else on the edit screen,
but only one stays on the edit screen and lets the user correct their
mistake on the spot, rather than starting all over again. Only the spectre
of undoing my work on the editscreen to put fields on a panel is keeping me
from embracing that option.
I'm also open to any and all suggestions, if the answer to my original
question is 'so sorry'. Thanks!
MDBloemker
(e-mail address removed)
about most things ASP.NET, as my background is primarily Lotus Notes
Development, and before that, DOS-based FoxPro.
Is there a way to group elements, such as a set of textboxes and related
labels, in effect giving them a common group name that could then be used to
disable/enable other elements on the page? For example if I have a
_textChanged event on a textbox that detects an error, it would be lovely to
be able to hide all the other controls on the page, to reinforce the notion
that the user really can't do anything until they fix the error in the
original textbox. I've dealt too often with users who need to be hit over
the head with a sledgehammer like that.
Right now, I see my choices as: 1) putting the controls to be hidden in a
panel and hiding the panel, which is not an ideal solution because it would
involved redesigning the screen; or 2) immediately redirect the user out of
the edit screen back to the main screen, and display a bright red error msg
in my lblErrMsg label telling them what they just did wrong. Both accomplish
the goal of keeping the user from doing anything else on the edit screen,
but only one stays on the edit screen and lets the user correct their
mistake on the spot, rather than starting all over again. Only the spectre
of undoing my work on the editscreen to put fields on a panel is keeping me
from embracing that option.
I'm also open to any and all suggestions, if the answer to my original
question is 'so sorry'. Thanks!
MDBloemker
(e-mail address removed)