Chip,
I had used the keyboard event by using ConnectEvent if you saw my
solution. I did not make it global, and did not sort it down to one window,
or check for just the tree view.
I could test your approach and see if it would differentiate between the
menu and the tree view inside the same dialog. I was not sure if it would
work or the exact way to sort out the menu from the tree view, if it was
even possible. Your example only shows how to set up an event to watch.
I just decided to make the key event once the keydown was fired and
watch which key was going up when it ended.
If the key was the spacebar and had no modifiers, I assumed it was just
the spacebar and was satisfied, along with the treeview flag being set. I
figured if a person had more than one key down, (with modifiers,) they were
not interested in just the spacebar.
I am not sure there may be a time that could happen in more than one
window, but maybe, anything is possible in windows.
I was doing something quick so I could get some other work done and have
not gone back to it to try what you did in class 17.
Since my approached work, I just decided to work with it.
NOTE:
You mentioned there about the up arrow or down arrow, my entire
complaint about the app tree view manual was nothing was in the place it
should be, scattered around, and you have to piece everything together to
figure exactly what they are talking about.
Now first you go down the tree view and press enter on the topic, then
use the moss, but the mouse does not mention likes there unless you press
the left mouse and cursor down and find a link to another list. At the time
I did not do that in all cases and missed links to certain descriptions, but
instead of just the word and a link around it, maybe just saying see... or
onclick... then the mouse could be used.
Anyway, this topic has gone far enough and will have to wait and see if
a new app reference comes out in the future.
Just have to find a road map to read a road map...
Bruce
Sent: Saturday, August 13, 2011 8:26 PM
Subject: RE: Tree view
and, class #17 is all about the key object (and of course has examples of
using it in onKeyUp and onKeyDown).
-----Original Message-----
From: Aaron Smith [mailto:[email protected]]
Sent: Friday, August 12, 2011 8:15 AM
To: [email protected]
Subject: Re: Tree view
On 8/11/2011 11:54 PM, BT wrote:
> Having done this gives more a feeling on how the object model
> book is structured by still badly in need of better understanding.
> Such as a key object, but how do you get a key object? Things like
> that which are very difficult to get out of that manual. You can find
> the keys object and how it is gotten, but where the key object is, I
> could not find and did not want to waste more time than I already had
done.
All of the objects are listed alphabetically -- you can simply press the
letter K until Key is selected. In addition, the main section of the Key
object talks about all possible places to obtain a Key object from. You can
also use the Search feature to locate any reference to the Key object.
How can we make this better?
Thanks,
Aaron
--
Aaron Smith
Web Development * App Development * Product Support Specialist GW Micro,
Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information pertinent to
your situation when submitting a problem report to the GW Micro Technical
Support Team.
