Tree click event details

[DavinChurch]

APL+Win provides considerable "click" information that Dyalog does not provide. In particular, ItemDown can tell me which item was clicked on but it does not give me enough other information about the clicks. The MouseDown event can tell me the mouse (pixel) location, which I need during this event, but it doesn't come with the other ItemDown information. In addition, I need the specific-location information from the TreeView_HitTest API call for whichever item was clicked (detailed list available upon request). Perhaps there could be a method to perform the API call for a given item click? This could give me what I need without impacting existing applications. In addition, if these are regular methods then I could get EWC to support them as well for future portability needs to non-Windows systems. Alternatively, you might add another event to provide the additional details directly and all at the same time.
The double-click events have the same problem.

[johndaintree]

The last item of the ItemDown and ItemUp message already includes the hittest information (as long as you click on an item). Do you really need more than this?

[DavinChurch]

The information that APL+Win is reporting for a click is:

• Cell Row
• Cell Column (on any column)
• Click Location: image, label, imageuser, above, below, toleft, toright, aboveleft, aboveright, belowleft, belowright, nowhere or '' (empty vector)
• Shift keys: +Shift, +Ctrl, +Alt
• Mouse position (row, column)
• Mouse key pressed: left, right

I seem to only be able to get some of this information, and then only from different events.

[johndaintree]

Yup, we don't report all of it. But I think the useful bits. Do you realy need the mouse coordinates as well, given hat most of the hittest information is provided in the message - what are you going to so with it? Likewise do you need an ItemDown event when you're not in an item?

[DavinChurch]

I personally haven't used the mouse coordinates very often with this event that I can remember, but that's not to say that others don't. And sometimes there's an on-edge situation that actually doesn't clearly represent an item being clicked, but I still get this event. In APL+Win, this is called the onClick event, so it isn't defined to be an item specifically. And it doesn't have a separate MouseClick event, relying instead on this to give them that information. So I'd say that they'll occasionally need this, especially if they're doing their own calculations of detailed position rather than relying on the more general area of the cell. It's difficult to combine the Mouse* event data with this when I have to respond to a single event all at once.

This event also tells them what they want when they've clicked outside the reporting area altogether (which I have needed myself on occasion, to de-select what I was working on, for instance). And if there's nothing in the list at all, it's tougher to tell if they've clicked somewhere anyway.

[DavinChurch]

I have run into additional places where APL+Win allows this sort of information to be obtained with a method call. So the basic functionality might be needed in several places.

[DavinChurch]

There is apparently a HitTest method for APL+Win classes CommandBar, Listview, Selector, Status, Tree, & DateTime. Perhaps we should group all these information needs together into a single method call that could be used by any of these upon demand, rather than changing what is automatically being returned by the standard events?

Issue #35 is also related to this and perhaps we should combine these together?