• Products
    • Isadora
    • Get It
    • ADD-ONS
    • IzzyCast
    • Get It
  • Forum
  • Help
  • Werkstatt
  • Newsletter
  • Impressum
  • Dsgvo
  • Press
  • Isadora
  • Get It
  • ADD-ONS
  • IzzyCast
  • Get It
  • Press
  • Dsgvo
  • Impressum

Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags

    [LOGGED] Keyboard watcher behavior

    Troubleshooting and Bug Reports
    3
    6
    784
    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.
    • jfg
      jfg last edited by Woland

      I don't know if it is normal and I don't understand something.

      Normally I use the Keyboard Watcher actor with "down" as direction e.g. with the key '1'.  If I hit  1 to fill a value in an actor nothing happen with the keyboard watcher. I thought it is the normal behavior. But if I select "up" or "both" the keyboard watcher become active if I hit the key '1' even if I am tiping in a value field of an actor.

      It is the normal behavior?

      best

      Jean-François

      Test Keyboard watcher.izz

      • Izzy 3.2.6
      - MacBook Pro M1 Max 16" 64GB RAM, Mac OS 15.3.2 Sequoia
      - Mac Pro 5.1 middle 2012 (3,33 GHz 6-Core Intel Xeon, 32GB RAM, Radeon RX 580 8 GB ),
      Mac OS 10.14.6 (Mojave)
      - Mac mini Pro M4, Mac OS 15.3.2 Sequoia

      • A range of deployable older Macs
        Located in Bremen, Germany
      Woland 1 Reply Last reply Reply Quote 0
      • Woland
        Woland Tech Staff @jfg last edited by Woland

        @jfg

        The file you sent works just fine for me in 3.0.7 when set to down

        https://recordit.co/ZjY5M4KaXf

        When it's set to up or both, it's going to trigger when you release the key because once a key is released, the "focus" is no longer being hogged by the actor you're typing into. 

        I am unsure if this is the ideal behavior, but it works this way in 2.6.1, so technically it is the expected behavior.

        I have brought this to @mark 's attention so we'll see if it's something that is a bug or not.

        TroikaTronix Technical Support
        New Support Ticket: https://support.troikatronix.com/support/tickets/new
        Support Policy: https://support.troikatronix.com/support/solutions/articles/13000064762
        Add-Ons: https://troikatronix.com/add-ons/ & https://troikatronix.com/add-ons/?u=woland
        Professional Services: https://support.troikatronix.com/support/solutions/articles/13000109444

        | Isadora Version: all of them | Mac Pro (Late 2013), macOS 10.14.6, 3.5GHz 6-core, 1TB SSD, 64GB RAM, Dual AMD FirePro D700s |

        jfg 1 Reply Last reply Reply Quote 1
        • jfg
          jfg @Woland last edited by

          @woland

          Thank you. I was not sure if it was the right behavior but your explanation:

          When it's set to up or both, it's going to trigger when you release the key because once a key is released, the "focus" is no longer being hogged by the actor you're typing into. 

          is logical and it seems to be indeed the correct way for this actor to work

          best 

          Jean-François

          • Izzy 3.2.6
          - MacBook Pro M1 Max 16" 64GB RAM, Mac OS 15.3.2 Sequoia
          - Mac Pro 5.1 middle 2012 (3,33 GHz 6-Core Intel Xeon, 32GB RAM, Radeon RX 580 8 GB ),
          Mac OS 10.14.6 (Mojave)
          - Mac mini Pro M4, Mac OS 15.3.2 Sequoia

          • A range of deployable older Macs
            Located in Bremen, Germany
          Woland mark 2 Replies Last reply Reply Quote 1
          • Woland
            Woland Tech Staff @jfg last edited by

            @jfg

            I can totally see how it could be undesirable behavior in certain cases though

            TroikaTronix Technical Support
            New Support Ticket: https://support.troikatronix.com/support/tickets/new
            Support Policy: https://support.troikatronix.com/support/solutions/articles/13000064762
            Add-Ons: https://troikatronix.com/add-ons/ & https://troikatronix.com/add-ons/?u=woland
            Professional Services: https://support.troikatronix.com/support/solutions/articles/13000109444

            | Isadora Version: all of them | Mac Pro (Late 2013), macOS 10.14.6, 3.5GHz 6-core, 1TB SSD, 64GB RAM, Dual AMD FirePro D700s |

            1 Reply Last reply Reply Quote 0
            • mark
              mark @jfg last edited by

              @jfg 

              I have fixed this behavior for the next release. Now you should get 'up' notifications only when you would also get a 'down' notification.

              (Key ups are handled in a very different way than key downs internally, because most widgets (e.g. a text box) don't want them. Thus the problem you discoverved.)

              Best Wishes,
              Mark

              Media Artist & Creator of Isadora
              Macintosh SE-30, 32 Mb RAM, MacOS 7.6, Dual Floppy Drives

              1 Reply Last reply Reply Quote 1
              • jfg
                jfg last edited by

                Thanks

                Jean-François

                • Izzy 3.2.6
                - MacBook Pro M1 Max 16" 64GB RAM, Mac OS 15.3.2 Sequoia
                - Mac Pro 5.1 middle 2012 (3,33 GHz 6-Core Intel Xeon, 32GB RAM, Radeon RX 580 8 GB ),
                Mac OS 10.14.6 (Mojave)
                - Mac mini Pro M4, Mac OS 15.3.2 Sequoia

                • A range of deployable older Macs
                  Located in Bremen, Germany
                1 Reply Last reply Reply Quote 0
                • First post
                  Last post