Keyboard input



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 30/10/2012 at 11:58, xxxxxxxx wrote:

    I'm using R14 and I can confirm it works on a python tag, although only when I hit the play-button in the timeline.
    Phil



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 30/10/2012 at 12:17, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    I'm using R14 and I can confirm it works on a python tag, although only when I hit the play-button in the timeline.

    Yes your code works.
    We're talking about completely different things.
    I'm talking about plugins with keyboard or mouse input events == ToolData, ObjectData etc.



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 30/10/2012 at 13:55, xxxxxxxx wrote:

    I apologize for the confusion guys.
    I'm finding out that that the qualifier behaviors change a lot depending upon the specific case they are used in. And not really so much a Python vs. C++ differences kind of thing as I thought.

    This is what I've found:

    Python Scripts and Both Python & C++ tags:
    Only the Ctrl key needs to be pressed to get a return. No second key needed.

    Plugins (tool, object,etc..) Both Python & C++
    The Ctrl key needs a second key to get a return

    Plugins (GeDialog) C++ and Python
    When a button or other gizmo is being pressed or activated...Only the Ctrl key needs to be pressed to get a return. No second key needed.

    I had no idea the qualifiers behaviors changed so much. Depending on the specific type of script, tag, or plugin they are used in.

    Sorry for any confusion I may have caused.
    I had no idea they worked like this.

    -ScottA


Log in to reply