Hi Aaron,
Just got back from Ithaca and my construction ordering run. I was
talking about finding the assignment of the Key Object like the one for the
Keyboard. When doing the keyboard assignment that I used inside the tree
view event, I was able to get the other object assignment, but when using
the Key assignment it said, "No Object, in the words of, must have object"
But followed the same assignment that I used for the Keyboard.
At that point I did not want to figure out what was wrong, so I just
stayed away from it. Yes, I did find the Key just before the Keyboard. But
when looking at events and properties that wanted a Key Object, I could not
get it to work when attempting to use one of the properties requiring the
Key Object.
so, I probably could try again and see what I was doing wrong, but will
have to take a closer look at it to see what I did wrong.
I was trying to expose more of the keyboard properties and they resided
inside the Key Object.
What I did and posted works really nice and eliminates the need for a
hotkey assignment, which I had done before going to the key up event inside
the Keyboard Object.
You asked me what is needed?
What I discovered in the manual is a list of properties inside the
Keyboard and one is for Keys. Now that said without out saying, go to the
Keys object next on the manual list. But not saying it, just assuming that
is what you would do. So, lacking is an example instead of an assuming move
to that next object or way down the list or up the list.
so, what I am saying is, to have a really nice manual is to have an
example that shows usage in a simple way for all objects on the list, but
more than just saying key object is needed, but an actual example itself on
how to get that object. Granted experienced programmers don't need it, but
first time users do.
In other words a real time example that could even be tested inside the
Instant test app. Granted it means more work at your end, but there are some
real good examples in some places, but not every place in the WE Object
model manual.
As I said, I don't know why attempting to do a key object assignment it
failed to make an object and show no error until it looked for that object.
I will try to get that example and post it later, I just did not do it
after getting the error and just moved on to the keyup event which worked
perfectly once filtering out all but the spacebar or left mouse button
without modifiers.
sincerely
Bruce
Sent: Friday, August 12, 2011 8:15 AM
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.
