Giter Site home page Giter Site logo

Comments (6)

evilC avatar evilC commented on July 22, 2024 2

I am against anything using sliders, period.
UNLESS:
There is an equivalent text box to type exact value.
OR
You can use eg arrow keys to select exact value.
Otherwise, unless the slider is over 100px wide, it's impossible to select all values, and even then it's a right pain to select the exact value you want.

from ucr.

Snoothy avatar Snoothy commented on July 22, 2024

Great suggestion, I will look into this at a later point

from ucr.

evilC avatar evilC commented on July 22, 2024

What code is used for each plugin to handle deadzones is dictated by the plugin itself.
There would be nothing stopping you from writing new code, and making a plugin use that code instead for deadzones.
Plugin calling DZ function
Existing DeadzoneHelper class

So you could write an alternative DeadzoneHelper, then make a plugin that uses it.

from ucr.

Snoothy avatar Snoothy commented on July 22, 2024

Having a dual slider version and quad slider, as seen above, as input selectors would be a great addition to existing GUI configuration (int, string, enum)

from ucr.

evilC avatar evilC commented on July 22, 2024

A thought - given that the DZ on each of the scales is identical, a linear sensitivity option of <100% would achieve the same result, so all the examples in the above image are currently supported by the AxisToAxis plugin

from ucr.

diVineProportion avatar diVineProportion commented on July 22, 2024

I completely agree about having the text box to help hone in on the specific value.

The DZ are not necessarily identical on each end. I'll give you an example. First I will point out that the GUI I referenced in the OP was from the Saitek (now under Logitech) X52 Professional and I didn't think to show one of it's other features. If you right clicked in the one of the DZ areas where you see the current DZ value, you get this:

image

So the identical linked DZ's work great for something like my RX axis seen here
zxfievvepv

But what about the case of my throttle quadrant where physically I have each of the axis set at 50% (Throttle, Pitch and Yaw are all equal in straight line right at 50%), but logically they appear like this:
image

If I didn't have the ability to unlink the DZ's, I'd be forced to sacrifice axis positions as seen here

image

Whereas unlinking the axes would allow:
image

You may be wondering why exactly i care to do this when they are not logically at 50%. The thing is that it isn't important what they are at, rather that I know i can physically put each axis at the physical 50% mark, and I know that they will be residing in a DZ and not interfere etc,

from ucr.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.