HISE Logo Forum
    • Categories
    • Register
    • Login

    Knob min & max not setting the boundaries when equal.

    Scheduled Pinned Locked Moved Bug Reports
    1 Posts 1 Posters 20 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ustkU
      ustk
      last edited by ustk

      @Christoph-Hart Well, the first thing one might say is why the heck you want min and max to be equal?

      The scenario is, when you have a loop setting for instance, you set the min and max according to the range you allow a cursor to move. Now imagine the end of the loop is fully set to the right, end the start is at its max to the right as well. You obviously don't want the end to be able to move anymore, right? so you set its min to 1 and voilĂ , the loop is constrained to the value of 1, the knob can't turn... Well, but no... when both min & max are equal, the knob behaves like it's 0 to 1, while there should be a safety.

      • In the property panel, when you set min & max the same, the component is automatically deactivated so you can't use it. But as soon as you recompile, sadly it's activated again.
      • When min & max are set equal by the script, there's no deactivation at all

      Hise made me an F5 dude, browser just suffers...

      1 Reply Last reply Reply Quote 0
      • First post
        Last post

      27

      Online

      1.9k

      Users

      12.5k

      Topics

      108.6k

      Posts