Default .xml Per Project
-
I think this can be tucked into Settings > Project as a string entry.
If non-empty, on HISE start or project load, it will attempt to load the .xml file by name (already some sort of implementation like this exists as it always asks to load the last used xml when loading a project).
99% of the time, you're opening HISE to work on a current project. Unless you have gigs of samples mapped that aren't folded into a monolith, xml load is near instant.
This would skip having to go File > Recent Files > preset.xml every time HISE is opened.
-
@aaronventure i only use one XML per project. Git handles versioning and for everything else i use .hip
-
@d-healey I do too, that's why I would like to have the option for it to load immediately on HISE load.
-
@aaronventure aha I see, I just press enter so hadn't paid it much attention
-
@d-healey when launching HISE or project change? For project change, yeah, enter works, but for launching HISE it's always navigating to File > Recent Files > preset.xml , unless I'm missing something.
-
@aaronventure I think you're right
-
@aaronventure That would be great ++
When compiling DSP Networks having to reopen HISE makes it much more streamlined if it will load up the same .xml as before or if we can just set a default XML.
-
@oskarsh Also the same workspace and script editor tabs but one step at a time
-
@oskarsh you don't need to open the XML to compile the project's networks
-
@d-healey I know :)
But if you want to test it in context with your project you surely need to open the correct xml
-
@oskarsh said in Default .xml Per Project:
the correct xml
You have more than one? :p
Most of the time I open HISE once to work on my project, and close it when I'm done. The rest of the time I want to open a blank preset for making little test projects. So a default xml thing isn't so useful to me. But maybe it would be better if when you open HISE it shows you a prompt asking if you want to reopen the last xml, then you can hit enter or esc depending on what you want to do?
-
@d-healey I have one main xml file named like the project and smaller stripped down versions for testing. Once a plugin reaches a certain level of complexity I like to branch out and create a new one to test complex features in isolation.
I often also have a Waveform, Filter, Arp combo in one xml to test the audio and the scriptfx networks. So that I can click click click to have a good sounding working setup. I mainly work with FX Plugins.
I think having a prompt where we can just press enter or escape would be a very good compromise. I think this already exists when changing projects.