Rogutes wrote:
Benjamin Johnson (2011-10-21 00:03):
Having it consistent over all text inputs and configurable via> >keysrc sounds reasonable to me. I don't know the keysrc details> >though, so I might miss something.> >Cheers,> JohannesHaving input/insert mode and macros in keysrc would be interesting, if nottoo complex. Look how indecipherable your quotations are.
Sorry about that. My mail client (Opera Mail) seems to mangle things from time to time, but frankly I'm not too sure why.
Other than that, I have to agree with most points, because you seem to have done more homework than I have.
I lose sleep over this sort of thing. It's the little things that make or break a user interface; big problems aren't as bad, because if they're obvious enough you can learn to work around them. (Not that I mean that to imply anything about Dillo's UI!)
Shift-{Left,Right} doesn't do anything here and I would expect it to select text [I guess conventionally]. Ctrl-A selects all text in other FLTK apps, so dillo must have most input boxes covered with the CustInput class. ---- Rogut?s Sparnuotos
Looking through the code, there appear to be three(!) different classes: - CustInput in src/ui.cc - CustInput2 in src/dialog.cc - CustInput3 in dw/fltkui.cc Thanks for mentioning that -- I hadn't noticed the other two. Somehow, it seems just a little excessive... ~Benjamin