search

MrKepzie / Natron

Open-source compositing software. Node-graph based. Similar in functionalities to Adobe After Effects and Nuke by The Foundry.
www.natron.fr
GNU General Public License v2.0
1.49k stars 164 forks source link

Scrolling fractions of a point in float inputs #149

Closed throwcomputer closed 10 years ago

throwcomputer commented 10 years ago

Currently if you put your cursor into a floating point input box in any node, mouse scrolling only manipulates the number in whole point increments. This needs to allow for changing the number in any fraction of a point by placing the cursor at any position in the fraction of the decimal and using the mouse scroll or up and down keys to scroll at that decimal power, instead of the whole number.

Eg: if the cursor is placed at 0.0|0 (at the hundredth of a point) - expected result on scrolling up = 0.01, actual result = 1.00

blackearth2014 commented 10 years ago

Throwcomputer thanks for adding this issue. I was just experience that issue late last night.

devernay commented 10 years ago

Actually, the floating-point parameters have an OFX property called "increment", which should be a reasonable increment for that value. By default, it's 1. If you see wrong increments in some of our plugins, please point these out explicitely (parameter "blibli" of plugin "blabla"). What you describe is a Nuke behaviour. I agree it's a nice feature, but is it commonplace in other software, too? We don't need to clone every single Nuke feature. Fixing it at the source (via the increment property) is better IMHO. That nuke-like feature could be implemented, but I'm leaving it for later.

throwcomputer commented 10 years ago

Transform>ScaleX, Transform>Scale or any property of Transform. ChromaKeyer does not work as well.

GradeOFX works with this feature. This is as many as I have personally tested.

True you do not need to clone every feature of Nuke, yet you are making a very pointed effort in the development of Natron to basically create a direct copy of Nuke down to every minute UI detail. This causes a user to directly compare functionality between the two, given the users known response to behaviors already... so by choosing to ignore specific UI features of nuke, you are causing a clash of expected behaviors from your target users, and they are going to consider these instances bugs and failures of your program. If Natron didn't exactly mimic every detail of Nuke, I'd say no problem, pick and choose your UI features.

On Mon, Aug 4, 2014 at 9:10 AM, Frédéric Devernay notifications@github.com wrote:

Actually, the floating-point parameters have an OFX property called "increment", which should be a reasonable increment for that value. By default, it's 1. If you see wrong increments in some of our plugins, please point these out explicitely (parameter "blibli" of plugin "blabla"). What you describe is a Nuke behaviour. I agree it's a nice feature, but is it commonplace in other software, too? We don't need to clone every single Nuke feature. Fixing it at the source (via the increment property) is better IMHO. That nuke-like feature could be implemented, but I'm leaving it for later.

— Reply to this email directly or view it on GitHub https://github.com/MrKepzie/Natron/issues/149#issuecomment-51057572.

devernay commented 10 years ago

I added a reasonable "increment" values for the next release. In the beginning, we had zoomable sliders, (just like the the timeline), but it was a bit misleading...

fred

Le 4 août 2014 à 15:57, throwcomputer notifications@github.com a écrit :

Transform>ScaleX, Transform>Scale or any property of Transform. ChromaKeyer does not work as well.

GradeOFX works with this feature. This is as many as I have personally tested.

True you do not need to clone every feature of Nuke, yet you are making a very pointed effort in the development of Natron to basically create a direct copy of Nuke down to every minute UI detail. This causes a user to directly compare functionality between the two, given the users known response to behaviors already... so by choosing to ignore specific UI features of nuke, you are causing a clash of expected behaviors from your target users, and they are going to consider these instances bugs and failures of your program. If Natron didn't exactly mimic every detail of Nuke, I'd say no problem, pick and choose your UI features.

On Mon, Aug 4, 2014 at 9:10 AM, Frédéric Devernay notifications@github.com wrote:

Actually, the floating-point parameters have an OFX property called "increment", which should be a reasonable increment for that value. By default, it's 1. If you see wrong increments in some of our plugins, please point these out explicitely (parameter "blibli" of plugin "blabla"). What you describe is a Nuke behaviour. I agree it's a nice feature, but is it commonplace in other software, too? We don't need to clone every single Nuke feature. Fixing it at the source (via the increment property) is better IMHO. That nuke-like feature could be implemented, but I'm leaving it for later.

— Reply to this email directly or view it on GitHub https://github.com/MrKepzie/Natron/issues/149#issuecomment-51057572.

— Reply to this email directly or view it on GitHub.

MrKepzie commented 10 years ago

This has been implemented.

throwcomputer commented 10 years ago

awesome!

On Sat, Aug 9, 2014 at 10:04 PM, Alexandre Gauthier < notifications@github.com> wrote:

This has been implemented.

— Reply to this email directly or view it on GitHub https://github.com/MrKepzie/Natron/issues/149#issuecomment-51703908.