Page 2 of 2 FirstFirst 12
Results 16 to 22 of 22

Thread: LW 2020.0.1 Mac numeric input boxes problems?

  1. #16
    TrueArt Support
    Join Date
    Feb 2003
    Location
    Poland
    Posts
    8,367
    Usage of tablet is very important factor which should be mentioned in the bug report..
    Are you switching Input Method in options?

  2. #17
    I don't have a tablet, so at least in my case that's not the problem. I do have a Logitec Bluetooth mouse, but I've never had this problem in any other program.

    Erich

  3. #18
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    7,229
    I'm reasonably sure this stems from how Newtek is setting up the LW UI / Qt input focus relationships. This isn't new, Mac LW's UI historically has had problems in the area of window and UI gadget input focus, long before Qt entered the picture -- that's why I suspect the problem's more on the app coding side than the Qt side.
    John W.
    LW2015.3UB/2019.1.5 on MacPro(12C/24T/10.13.6),64GB RAM, NV 980ti

  4. #19
    I've tried several times unsuccessfully to screen record this problem. However, every time I go the other program - in my case Quicktime - to start the screen recording, when I go back to Lightwave, the problem has disappeared and all is working properly again. Well, at least now I know what to do to reset the bug.

    Erich

  5. #20
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    7,229
    Quote Originally Posted by ELinder View Post
    I've tried several times unsuccessfully to screen record this problem. However, every time I go the other program - in my case Quicktime - to start the screen recording, when I go back to Lightwave, the problem has disappeared and all is working properly again. Well, at least now I know what to do to reset the bug.
    You need to try and figure out the "trigger sequence" and then begin screen recording _before_ issuing the trigger sequence to make the problem appear. Switching away to another (gfx?) app then back to LW likely forces LW back to a "input-chain-valid" state, so you need to capture the issue without switching away until after you've captured it.
    John W.
    LW2015.3UB/2019.1.5 on MacPro(12C/24T/10.13.6),64GB RAM, NV 980ti

  6. #21
    ack ack Markc's Avatar
    Join Date
    Feb 2006
    Location
    England
    Posts
    1,651
    Quote Originally Posted by ELinder View Post
    I've tried several times unsuccessfully to screen record this problem. However, every time I go the other program - in my case Quicktime - to start the screen recording, when I go back to Lightwave, the problem has disappeared and all is working properly again. Well, at least now I know what to do to reset the bug.

    Erich
    Is this in 2020.0.2?
    Mac Pro (2010) OSX 10.14 RX580 Pulse LW2020
    (plugins: LWCad 2020, TFD 1443, Syflex 2018, StarPro 2020, ExrTrader 2020, Ubercam 2.0, Daz Mocap, DP Light 2020, Quadpanels 1.5)

  7. #22
    TrueArt Support
    Join Date
    Feb 2003
    Location
    Poland
    Posts
    8,367
    Hotkey screen-recording app..

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •