Hi Chip,
I understand you dilemma for an XML is a pain. I was just suggesting the
label first and any other event would be a click on the label which would be in
the Tree View. I guess you just have to improvise the rest depending on what
the starting point is.
Bruce
Sent: Frid
David,
Thanks for all the great ideas; I really liked them all.
Also, I don't know what I was thinking, but I can't use a treeview control
down the left, because I cannot define xml controls which occupy the same
space on the right, and have them switch out depending on which set I want
to
Hi Chip: I have used something like that for larger input screens.
Ya, just tab to a group, or a hot key, and then 3 or so tabs iinside the group
is fast and a sighted user can just click a box with the mouse almost instantly
- fast for both. If there were say 100 boxes that would be something di
Hi Chip,
Your welcome and I know a Tree View has it's limitations as David kind of
points out, in terms of tabbing when navigating down the list. For a list
allows you to make as many columns as you so desire.
So, doing the multi column list would accomplish the desired affect using
th
Chip,
Personally, I would have prefered a set of edit boxes, with each their hotkey,
for navigation. Now, it is perfectly well, to group them, and have each group
with its hotkey as well.
When comes to a treeview style, it may look nice and tidy for sighted people,
but for a blind user, it is n
Kevin,
WE xml dialogs don't have tabbed controls, but as you and Bruce and Rick
say, we have ways of simulating them. I like Rick's hotkey and showing
multiple groups (with labels), and having the hotkey jump between them. I
like it because a sighted user can see what's required at once, but I w
Thanks to you and Bruce for your votes and suggestions, but especially
thanks Rick for the idea of a hotkey to jump between groups.
I was bemoaning the lack of a multi-tabbed dialog in our xml dialogs, but
the hotkey which we all use (along with labeled groups) does the same thing!
How great is
Hi Chip,
I personally would choose to go down a list of groups, because it
certainly makes the app smaller. This may also have to do with small
and large screens and their resolutions. Have you experimented with
tab controls? This could fix your problems when working with large
sets of control
Oh Ya: If you group the controls you can have a hot key to jump between groups
for faster navigation - perhaps something like ctrl+tab or alt+tab or something
else. That way if you have 15 to 20 controls and group them into say 4ish
groups you can cut down the navigation dramatically and it's li
Hi Chip: As you said there are 2 basic layouts and which you pick depends on
the audience.
I often put a menu item in the view menu that allows the user to select which
view they want - ie ScreenReaderUserMenuItem.
You can then have 2 forms and display either one depending on if the
ScreenReader
10 matches
Mail list logo
