30EA1: "Connection" panel behavior on clicks of twisties and object names

Question

EA1 on Mac OS X.
SQLD's schema object tree has always been a little frisky in these ways:
* If i click the twisty (icon to the left of an object or category name) SQLD acts as though I asked it to do the default action on the object to the right of the twisty. I didn't. I really just wanted SQLD to reveal what's under / in the object. Now, if I click the object's name, maybe I'm asking for the default action like "open" (see below).
By being frisky, SQLD is likely wasting both my time and the resources it takes to do the default action.
* If I land on an object name by, say, using my down arrow key, SQLD acts as though I asked it to do something other than move the cursor (selection). I didn't. I think doing something should require that I do some other action like press the enter key, select a command from a context menu -- something.
Hence, this tree can't be navigated by keyboard. In (my idea of) a better SQLD, I could navigate the true with mouse or keyboard. I could open and close categories and object trees with + and - or left/right, I could use my platform's key for "show the context menu." Same for the mouse cursor.
* A specific case of the above two complaints working together is packages.
- I open "Packages," and see mine.
- I click the twisty left of a package name. SQLD opens the tree (good).
- But it also opens the package spec, which usually isn't what I want. More often, I want access to the body item.
- Then it closes the connection panel (because I keep that closed unless I need it).
So I'm left looking at a spec. Sure, there's a button for the body -- but I have to use the mouse cursor to get to it.

Answer 1

EA1 on Mac OS X.
SQLD's schema object tree has always been a little frisky in these ways:
* If i click the twisty (icon to the left of an object or category name) SQLD acts as though I asked it to do the default action on the object to the right of the twisty. I didn't. I really just wanted SQLD to reveal what's under / in the object. Now, if I click the object's name, maybe I'm asking for the default action like "open" (see below).
By being frisky, SQLD is likely wasting both my time and the resources it takes to do the default action.
* If I land on an object name by, say, using my down arrow key, SQLD acts as though I asked it to do something other than move the cursor (selection). I didn't. I think doing something should require that I do some other action like press the enter key, select a command from a context menu -- something.
Hence, this tree can't be navigated by keyboard. In (my idea of) a better SQLD, I could navigate the true with mouse or keyboard. I could open and close categories and object trees with + and - or left/right, I could use my platform's key for "show the context menu." Same for the mouse cursor.
* A specific case of the above two complaints working together is packages.
- I open "Packages," and see mine.
- I click the twisty left of a package name. SQLD opens the tree (good).
- But it also opens the package spec, which usually isn't what I want. More often, I want access to the body item.
- Then it closes the connection panel (because I keep that closed unless I need it).
So I'm left looking at a spec. Sure, there's a button for the body -- but I have to use the mouse cursor to get to it.