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

Thread: LW2018 is incompatible with Default Folder

  1. #16
    Quote Originally Posted by jwiede View Post
    Okay, I'm still seeing problems where having DefaultFolder active in LW2018.0.6 Layout causes app crashes when plugins attempt to put up a open/save file dialog. Wondering if the devs fixed the obvious in-app cases, but forgot some common paths used by third-party plugins, or similar.
    i'm also still having issues from time to time, but NT devs defined the case as closed as soon as default folder devs made the 'fix'. but maybe there's still hope NT will cure the pain with the next release if you can reopen the case.
    3dworks visual computing
    demo reel on vimeo
    instagram

    OSX 10.12.x, macpro 5.1, nvidia gtx 980 ti, LW2015.x / 2018.x, octane 3.x

  2. #17
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,495
    Quote Originally Posted by 3dworks View Post
    i'm also still having issues from time to time, but NT devs defined the case as closed as soon as default folder devs made the 'fix'. but maybe there's still hope NT will cure the pain with the next release if you can reopen the case.
    Hope springs infernal. I'll see what I can do.
    John W.
    LW2015.3UB/2018.0.7 on MacPro(12C/24T/10.13.6),32GB RAM, NV 980ti

  3. #18
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,495
    Quote Originally Posted by jwiede View Post
    Hope springs infernal. I'll see what I can do.
    Okay, I can't reopen the bug, because I didn't originally open it (IIRC, mine got noted as a duplicate), and I can't find my duplicate of the actual issue anywhere in my list to reopen.

    Can anyone else find the issue marked closed or duplicate in their list to reopen?

    I'm definitely still seeing issues with DF. I'm also seeing indications the problem is no longer on the St Clair Software side of things, but instead LW capturing/processing keyboard input when it shouldn't. I've seen similar in the "default" non-DF-present case, and I believe what Chilton is describing is essentially the same issue -- LW is capturing/processing input when that input should instead be going to file selection dialog-related operation instead of LW.
    Last edited by jwiede; 11-10-2018 at 06:30 PM.
    John W.
    LW2015.3UB/2018.0.7 on MacPro(12C/24T/10.13.6),32GB RAM, NV 980ti

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
  •