HISE Logo Forum
    • Categories
    • Register
    • Login

    jassert when restoring external scripts

    Scheduled Pinned Locked Moved Bug Reports
    external scriptjassert
    2 Posts 1 Posters 139 Views
    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.
    • d.healeyD
      d.healey
      last edited by d.healey

      HISE seems to only look in the ScriptProcessors folder for external scripts (not includes). This triggers a jassert BackendApplicationCommandWindows.cpp: 333

      Also if when you connect a MidiProcessor to an external file, that external file is the global script directory, I think it should add the {GLOBAL_SCRIPT_FOLDER} wildcard to the path in the xml and restore from that path.

      Libre Wave - Freedom respecting instruments and effects
      My Patreon - HISE tutorials
      YouTube Channel - Public HISE tutorials

      1 Reply Last reply Reply Quote 0
      • d.healeyD
        d.healey
        last edited by

        Link Preview Image
        External global scripts by davidhealey · Pull Request #316 · christophhart/HISE

        favicon

        GitHub (github.com)

        Ok I fixed the assertion. HISE was looking for external scripts in the ScriptProcessors folder and of course they weren't there, so it was triggering the jassert. But it didn't need to go searching for them anyway because external scripts already have their full path in the Script property of the xml.

        So I just skip the entire function if it's an external script - might make loading some projects a little faster too.

        The next issue is when you connect a script that's in the global scripts folder HISE was using an absolute path, which obviously isn't good if you decide at some point to move or rename one of the folders in that path.

        Now I've set it up so that if you connect an external script from the global scripts folder it will add the {GLOBAL_SCRIPT_FOLDER} wildcard to the path and it also will translate this back to the global path you've assigned in project settings when you reload the project. I've tested this within HISE and as a standalone build and it seems to work without issue.

        Libre Wave - Freedom respecting instruments and effects
        My Patreon - HISE tutorials
        YouTube Channel - Public HISE tutorials

        1 Reply Last reply Reply Quote 1
        • First post
          Last post

        38

        Online

        1.8k

        Users

        12.1k

        Topics

        105.0k

        Posts