TreeView: How to capture Enter?

[(Pete Cresswell)]

I've got KeyDown coding and it fires when other keys are pressed, but when Enter
is pressed, nothing.

I'd like to support the (standard?) Windows behavior of executing DblClick
processing when an item is selected and the user presses Enter

I got focus to stop moving to the next control via Tools|Options|Keyboard|Move
after enter....but now it just sits there and neither KeyDown nor KeyPress seems
to catch it.

Is this the end of the road?
--
PeteCresswell

[David Schofield]

On Sat, 08 Jan 2005 20:10:17 GMT, "(Pete Cresswell)" <x@y.z> wrote:

I've got KeyDown coding and it fires when other keys are pressed, but when Enter
is pressed, nothing.

I'd like to support the (standard?) Windows behavior of executing DblClick
processing when an item is selected and the user presses Enter

I got focus to stop moving to the next control via Tools|Options|Keyboard|Move
after enter....but now it just sits there and neither KeyDown nor KeyPress seems
to catch it.

Is this the end of the road?
--
PeteCresswell

Hi
The KeyDown and KeyUp events don't occur when you press the ENTER key
if the form has a command button for which the Default property is set
to Yes.

So maybe if you make sure it hasn't they will. You will have to to
trap and act on the enter key for command buttons yourself.
HTH
David

[(Pete Cresswell)]

Per David Schofield:

Hi
The KeyDown and KeyUp events don't occur when you press the ENTER key
if the form has a command button for which the Default property is set
to Yes.

So maybe if you make sure it hasn't they will. You will have to to
trap and act on the enter key for command buttons yourself.
HTH

No Command buttons w/.Default=True - and I tested that by putting a regular
ListBox on the same form. The regular ListBox's KeyDown event fires when
Return/Enter are pressed (KeyCode=13).

It's starting to sound like the TreeView's behaviour is somewhat different.
--
PeteCresswell

[David Schofield]

On Sun, 09 Jan 2005 22:21:21 GMT, "(Pete Cresswell)" <x@y.z> wrote:

Per David Schofield:

Hi
The KeyDown and KeyUp events don't occur when you press the ENTER key
if the form has a command button for which the Default property is set
to Yes.

So maybe if you make sure it hasn't they will. You will have to to
trap and act on the enter key for command buttons yourself.
HTH

No Command buttons w/.Default=True - and I tested that by putting a regular
ListBox on the same form. The regular ListBox's KeyDown event fires when
Return/Enter are pressed (KeyCode=13).

It's starting to sound like the TreeView's behaviour is somewhat different.
--
PeteCresswell

Hi
Um ...
You can set the form.KeyPreview = true and catch ENTER with KeyDown at
the form level, check that the treeview is active and in a suitable
state (use the treeview events to set up this) and then call your
doubleclick event. But the ENTER will still be passed to the treeview
control as KeyDown doesn't have a cancel argument.

Straightforward subclassing the treeview doesn't catch Enter, but if
you are up for heavy coding see
How To Prevent the ENTER Key From Firing in TreeView Control
http://support.microsoft.com/default...b;en-us;216664

This is written for VB.

It is a bold developer who deploys any Access app with treeview in it,
let alone one with subclassing!

David
HTH
David

[(Pete Cresswell)]

Per David Schofield:

It is a bold developer who deploys any Access app with treeview in it,
let alone one with subclassing!

I've got a couple out there with no reported problems.

("Reported" being the operative word....)
Anything special I should be on the lookout for?
--
PeteCresswell

[(Pete Cresswell)]

Per David Schofield:

ou can set the form.KeyPreview = true and catch ENTER with KeyDown at
the form level, check that the treeview is active and in a suitable
state (use the treeview events to set up this) and then call your
doubleclick event. But the ENTER will still be passed to the treeview
control as KeyDown doesn't have a cancel argument.

Still no-go.

I checked it with ?frmWhatever.Keypreview in the immediate window....and,
indeed, it still fires KeyDown and KeyPress for the space bar and other
keys...but not Enter.

I think I see why, though. The list is already using Enter to toggle nodes'
..Expanded. Hit Enter on a collapsed node and it expands...do the same thing
on an expanded node and it collapses.

I guess that about wraps it.... I guess I'll just trap SpaceBar and tell the
users to learn to love it.
--
PeteCresswell

[David Schofield]

On Tue, 11 Jan 2005 00:44:22 GMT, "(Pete Cresswell)" <x@y.z> wrote:

Per David Schofield:

It is a bold developer who deploys any Access app with treeview in it,
let alone one with subclassing!

I've got a couple out there with no reported problems.

("Reported" being the operative word....)
Anything special I should be on the lookout for?
--
PeteCresswell

Hi
Problems with common controls arise mainly in MDE/run time systems
when older or newer versions of the DLL are on the user's PC
David

[TheSmileyCoder]

I was just myself searching for a solution to the above problem without any luck, but as I did find (partly based on the above) a solution I will post it here, even if it is a quite old thread.


First you must ensure that the Form previews the key pressed before the control. Enter your form properties and find the property called "Key Preview" and set it to TRUE.

This part is optional, but I decided to add a public enum to make it easier for myself to see the keycodes, so this goes into a public module:

Public Enum Keys
   Enter = 13
   Spacebar = 32
   NoKey = 0
End Enum

Now write code for the Key_Down event of the form, and notice I use it for both my treeview and my listview:

   'Only react to keyStroke=enter(13)
   If KeyCode <> Keys.Enter AND Keycode<>Keys.Spacebar then Exit Sub
 
   'Respond accordingly to which control is the active control
      Select Case Me.ActiveControl.Name
         Case Me.TreeProjects.Name
            'Treeview is active, determine active node (if any)
               Dim tv As TreeView
               Set tv = Me.TreeProjects.Object
               If Not tv.SelectedItem Is Nothing Then
                  Custom_TreeProjects_NodeSelect tv.SelectedItem
               End If
 
            'Cancel enter keystroke
               KeyCode = Keys.NoKey
 
         Case Me.listReports.Name
            Select Case KeyCode
               Case Keys.Enter
 
               Case Keys.Spacebar
                  Dim lv As MSComctlLib.ListView
                  Set lv = Me.listReports.Object
                  If Not lv.SelectedItem Is Nothing Then
                     OpenReport getID(lv.SelectedItem)
                  End If
            End Select
            'Cancel enter keystroke
               KeyCode = Keys.NoKey
 
      End Select
 
exitSub:
   Set tv = Nothing
   Set lv = Nothing
 
 
End Sub

The Original poster doesn't say so, but I think when he tried this, he kept using the Treeviews KeyDown event, after turning on Key Preview, and thus failed to move the tracking into the forms Key_down (Which occurs any control reacts to Key_Down, thus why it is called Preview)