Customize Dialog and Procedure On First Plugin Load (hr1 sample archive)

[gorangrooves]

Hey guys,
Is there a way to change the behavior of that initial dialog pop-up for hr1 files when a compiled plugin is installed for the first time?

I don't think I will be using the hr1 procedure as I think it adds unnecessary steps for the user. I will have my installer install the samples in a location of user's choosing and would like the avoid the confusing dialog related to hr1 files extraction.

I want just to prompt the user to select the directory where they placed the samples and that's it.

Can I get rid of all the other stuff?

Even better would be if the installer could provide the plugin with the necessary info as to where the samples were placed by the user. This would cut yet another step.

Thanks.

[Lindon]

Under windows (its sorta similar for mac):

the initial dialog pop up simply adds a file to the AppData/Roaming/<vendor name>/<product name>/

called LinkWindows

thats a link file pointing at the location of your samples, as defined by the user in the dialog.

You could I suppose have your installer:

• ask the user where they want the sample placing

• create the folder structure

• create the LinkWindows file

• rinse and (nearly) repeat for Mac users

[Tod Slaughter]

@gorangrooves As far as I know if you supply the samples and the user places them wherever they want. On first load the plugin as you say will ask for the location. It's only if this step is skipped that problems start. Then it's a case of deleting the Linkwindows file as Lyndon has pointed out.

[gorangrooves]

Thanks @Lindon and @Tod-Slaughter .

Sweet. I found the location of that linkWindows file.

So, as long as that link file is found by the plugin in the expected location, there will be no prompt on the initial load. Correct?

[Christoph Hart]

@gorangrooves said in Customize Dialog and Procedure On First Plugin Load (hr1 sample archive):

So, as long as that link file is found by the plugin in the expected location, there will be no prompt on the initial load. Correct?

The result of this dialog is the creation of this file so if your installer creates it beforehand, it will never have to appear.

But be aware that there are many pitfalls with installers which lead me to this solution. The most difficult thing is to give the installer enough permissions to create the files at various locations (which is for some reason multiple times more difficult than giving an app these permissions).

[gorangrooves]

@Christoph-Hart Thank you. That's good to know. I think that some installers are more powerful than others with regards to permissions (from what I read). I will give it a shot, but if the installer doesn't set it up, the dialog is always there as a backup.

It would be nice if there was an option within HISE to select whether plugin will be provided with hr1 files or raw samples, which would affect the dialog prompt that pops up. That way, the most relevant dialog prompt would appear if needed.

[LeeC]

@gorangrooves Did you manage to find a custom installer solution or did you end up reverting back to the original hr1 pop up solution?

[gorangrooves]

@LeeC I have not created a solution for this as of yet. I was planning to set up the installer to create the necessary reference file. There was some talk about this same issue recently here on the forum. Have a look at the recent posts, there may be an answer to it.