Why can’t I tab through fields such as the ones in the transform dialog, and why can’t I select text like in every other piece of software ever written in the history of computer software?
I someone know how to accomplish this please step forward. I hate having to insert my cursor and then hit the delete key fifty times to clear a field before entering a new value.
You can copy/past between fields. Put the cursor on a text/number field (you don’t have to click it) and press Ctrl-C to copy and Ctrl-V to paste, it even works with colorfield!!! They aren’t ridiculous and counterintuitive only because you don’t know how to use them…
Martin[/quote]
would it be hard to add.? somethin like if you edit one feild and press tab you could jump to the next one.
I hava feeling this would need to change some deep code, but i’m not sure.
Yeah, I wish I could Switch between Text fields like Gabio said, it kind’a takes to much clicking of the mouse to switch, while my hands are occupied on the Keyboard. :-?
As simple as that.[/quote]
would it be hard to add.? somethin like if you edit one feild and press tab you could jump to the next one.
I hava feeling this would need to change some deep code, but i’m not sure.[/quote]
For one thing, the buttons definitions would have to include a tab order. That or use the order of create. Eitherway, I don’t think the buttons are kept anywhere as an ordered list (may be wrong thought).
(to get sidetracked into technicalities…)
Actually, the buttons are kept in a list, belonging to each uiBlock, and each button points to a but->next (you can see around line 2630 in tuhopuu3, interface.c). This is how the arrow keys to highlight in menus work, since menus are just uiBlocks too, but laid out vertically and they look different.
The tricky part is though, that what you really want is to accept the TAB key inside the do_but_TEX function (while you’re typing something) and get it to move to the next button. Actually, that gives me an idea but it probably won’t work…
(to get sidetracked into technicalities…)
Actually, the buttons are kept in a list, belonging to each uiBlock, and each button points to a but->next (you can see around line 2630 in tuhopuu3, interface.c). This is how the arrow keys to highlight in menus work, since menus are just uiBlocks too, but laid out vertically and they look different.
The tricky part is though, that what you really want is to accept the TAB key inside the do_but_TEX function (while you’re typing something) and get it to move to the next button. Actually, that gives me an idea but it probably won’t work…[/quote]
If that’s the case then, you can probably just stick some code in the button keyboard handling (where Shift-Backspace is handled). No idea how you’d transfer the focus though.
(to get sidetracked into technicalities…)
Actually, the buttons are kept in a list, belonging to each uiBlock, and each button points to a but->next (you can see around line 2630 in tuhopuu3, interface.c). This is how the arrow keys to highlight in menus work, since menus are just uiBlocks too, but laid out vertically and they look different.
The tricky part is though, that what you really want is to accept the TAB key inside the do_but_TEX function (while you’re typing something) and get it to move to the next button. Actually, that gives me an idea but it probably won’t work…[/quote]
If that’s the case then, you can probably just stick some code in the button keyboard handling (where Shift-Backspace is handled). No idea how you’d transfer the focus though.
Martin[/quote]
Now, if we could just do thinking like this in more important areas LOL
What makes you think analytical thinking doesn’t happen elsewhere in discussing blender code? It happens all the time. And, what, you’re saying that there’s an area of Blender more important than ui coding??! (hehe :P)