Repository navigation
Replies: 4 comments 14 replies
|
@prmod3d Thanks for the thoughtful idea, and I know that "giddy" feeling with such fields. I'd rather not add it, though: the properties and settings panels scroll with the wheel, so a number would change by accident whenever the pointer passes over a field, and the question of which digit to change needs a rule or one more setting. For changing a value with the mouse alone, almost every number field has a slider under it. If you find a field where one is missing, tell me which and I'll look at it. |
|
I could see where the OP's idea would be useful as im native to this feature in adobe illustartor (I make graphics decals and stickers for atvs, utvs, bikes, trailers etc) and this is a super sweet feature I enjoy on there. when I tried on layerling I made a bit of a sad face when it didnt work. to be fair though, many programs dont utilize this feature though. haha. #spoiled I guess. hahaha. however in hens defense, I can see where it would take some work to make it so ppl dont mess it up. |
|
@WagnerBoyzRacing thank you, it helps to hear how it works in Illustrator. The reason I held back is the one you name: the side panels scroll with the wheel, so a number would change whenever the pointer passes over a field. I decided to leave it as it is. Most fields have a slider under them for the mouse alone. |
|
@prmod3d, @WagnerBoyzRacing thank you both, the detail you gave changed my mind. My worry was that a number would change when the pointer passes over a field while you scroll the side panels. If the wheel works only in a field that you have clicked (as you describe for Illustrator), that does not happen. I added it: click a number field of the properties, then the wheel changes the value, by one unit a notch (a millimetre, a degree, a sixteenth of an inch), with Shift ten times as much, with Ctrl a tenth and with Alt a hundredth. A field that you have not clicked leaves the wheel to the panel. It comes with the next release; I'm not touching the sliders for now. |
Uh oh!
There was an error while loading. Please reload this page.
Here's an idea that's definitely not urgent, nor even needed if you deem it to be ridiculous! Perhaps it could be considered a future coding challenge when there's nothing left to do...
Most design programs. layerling included, require a lot of swapping back and forth between the keyboard and mouse. We get used to this and it becomes second nature. Some people are keyboard warriors, learning all the shortcut keys and preferring to spend most of their time on the clickity-clacks, while others prefer to navigate the GUI with a mouse and execute most actions that way.
The one action that usually always requires a keyboard (to the constant dismay of mouse users) is entering text values in a field. Use the mouse to select a field, then switch to keyboard and back to mouse. Ugh!
There's an elegant solution that some programs use which is to continue using the mouse (and specifically the scroll wheel) to roll through incrementing/decrementing digits in an existing number value. Not to be confused with a drop-down of pre-defined values or the up/down arrows embedded on the left side of fields such as some of those used in Orca Slicer and mobile device apps (although that method would work as well); but rather simply selecting the field and spinning the scroll wheel to modify values.
It's very slick, (and I get somewhat giddy when I see these!) but it also has some limitations which is probably why it's not seen more often. The most obvious is determining which decimal place number to change. Using the lowest value (say in the tenths place) would allow for the most precise changes, but would take a long time if you want to change 224.65 to 310.65.
I suppose some sort of logic could be used to determine what the most likely-to-be-changed decimal place would be of a number in any given field; or maybe placing the cursor I-beam next to the place-digit you want to change; or perhaps let the user decide by providing a default option in the Settings. And of course any keyboard input would be an automatic override method of entry.
Anyway, just thought I'd put it out there as I find these sort of value-changing fields extremely convenient when I stumble across them. For sure they're mostly an unnecessary bit of coding pizzaz and flourish, even though they can also make workflow a bit easier and more productive.
All reactions