Any new insights, workarounds or better a solution for folders resumed/isOpen issue?

Any new insights, workarounds or better a solution for folders resumed/isOpen issue? I haven’t found any that’s properly working. It’s really annoying 😩

]]>

7 Commentsto Any new insights, workarounds or better a solution for folders resumed/isOpen issue?

  1. Anonymous says:

    < ![CDATA[

    What exactly do you want to get in which situation?

    ]]>

  2. Anonymous says:

    < ![CDATA[

    He posted a bug report.


    If I remember correctly (and I can be wrong so correct me) before, a script in the resumed event had the isOpen boolean to false when opening the folder (the script was launched before the folder was opened, or something like that)


    Now that boolean is true, so you can’t detect whether the script was run with the folder already opened or when opening it.



    Lutz Linke​ I think the best solution is a script in the run event of the folder item.

    ]]>

  3. Anonymous says:

    < ![CDATA[

    TrianguloY There is no “run” event for folder. The shortcut has “tap” event, but that’s too early for Material Folder event. I use resume and pause event. But these are also fired when editing inside opened folder or when app is launched from folder and closed.



    I was refering to this bug report:


    https://plus.google.com/+LutzLinke/posts/Z1AgPpET9A4



    Also it was reported that DimDesktop script is also broken because of this issue.

    ]]>

  4. Anonymous says:

    < ![CDATA[

    Lutz Linke yes, sorry. I mean the tap event.


    Can’t you set a script there that opens the folder and runs the other script? It should be the same (but from what you said it seems not)

    ]]>

  5. Anonymous says:

    < ![CDATA[

    Lukas Morawietz It’s the issue you already reported:


    https://plus.google.com/+LukasMorawietz/posts/M4ndLhUuVKZ

    ]]>

  6. Anonymous says:

    < ![CDATA[

    TrianguloY Tap is before folder opens. Open programmatically might work with proper delay timing etc. But it’s just a workaround. And probably not accurate. Paused/closed script wouldn’t be handled improperly, still.

    ]]>

  7. Anonymous says:

    < ![CDATA[

    For the dim background the fix was easy, because it doesn’t distinuish between those two situations anyway. I can’t help you, sorry.

    ]]>

Leave a Reply

Your email address will not be published. Required fields are marked *