ctrl-a doesnt work in the search field

[bbrendon]

When pressing ctrl-a when the cursor is in the search field, it selects all the text in the code view. It should select all the text in the search field.

https://s3.amazonaws.com/uploads.hipchat...upload.png

[Dean Roddey]

The editor window is probably seeing it via the accelerator table so it gets eaten before it gets to the entry field. I'll take a look at it. I think I let it still see input when the search has the focus so that stuff like F3 (next) work. I could I guess just give the editor tab its own accelerator table and have it send commands to the editor instead, then I wouldn't let the editor see any input when the search tab has the focus.

[Dean Roddey]

OK, I addressed this for 5.0.5, plus once I got in there I realized there were a lot of things to deal with. And, then I wanted to make the improvement of having the active tab be colored differently when the tabbed window has the focus vs. not, so that you can see where you are when you tab around. Currently the active tab is white and it doesn't indicate if that tabbed window's active tab has the focus or not, so you can get lost if you are tabbing around in the Admin Intf.

That turned out to be just completely PSYCHOTIC. It almost destroyed my brain but I think I have it working right now. It really helps a lot to have that

I also figured out how to get rid of Scintilla's (the source editor engine) annoying habit of selecting all of the text when you tab into one of the source editor tabs, which is much nicer as well. So you don't lose your position when you tab around and pass through the active source editor tab.

There's also the issue of Ctrl-F4/F6, which close tabs and cycle through tabs. That was part of what was causing the Ctrl-A problem. Because we have nested tabbed windows in the CML IDE, the nested tabbed window would eat those keys and you couldn't move through the top level tabs via hot keys. So I let the main window see the keys first, to get around that. But that meant that it could eat keys that were really supposed to get to something else.

Of course once I fixed that, then now I was back to not being able to use hot keys on the outer tabbed window in the CML IDE. The inner tabbed window would always get them. I didn't know of any standard for this, so I just made one up. If you do Ctrl-Shift-F4/F6, then it always targets the outer one. Regular Ctrl-F4/F6 targets the one that would naturally see those keys. So you can now do hot keys for both tabbed windows. If anyone knows of any more standard way of dealing with such things, let me know and I'll try to do it that way.