Factory vs. User Presets
- 
 I despair just at the topic Factory vs. User Presets 
 As in all my purchased plugins, I would like to prevent the user from overwriting factory presets.
 He should be able to create user presets himself.How do I make it so that he can not overwrite factory presets? 
 But he can create user presets?
 With the standard preset browser???
- 
 @MikeB - you cant (I think), you have to do what all the developers of your purchased plugins did - and write your own preset system. 
- 
 This has been requested a few times... 
- 
 @d-healey said in Factory vs. User Presets: This has been requested a few times... This wish has some here as I have seen 
 Is there any way to get this back on the agenda?
- 
 The only way I can think of ATM is to make our own preset browser, so you can discriminate between a User and a Factory folder and apply rules in consequence... 
- 
 What happens if you make the preset files themselves read only? 
- 
 I was thinking about this. I didn't try it yet. But I was thinking of saving my Factory preset with a specific bool with Save Preset btn visible false hidden from the user. Then having a user folder that contains a preset that has btn visible always set to true. It's something floating in my head. 
- 
 @marcLab That's a clever idea. Can you change the hidden state of the button dynamically? 
- 
 This is my current workaround - you put the browser and two buttons in one panel 
 One button "User" - when clicked the panel extends by 50pixel and the buttons Add, Rename and Delete become visible
 One button "Factory" - when clicked the panel decreases by 50 pixels and the functions become invisible.
- 
 My wish would look like this { "ShowSaveButton": false, *"Show Searchfield": true/false, *"Show Factory-Folder": name here *"Show USER-Folder": name here *"Set Factory presets NOT overwriteable": true/false, *"Set User presets writeable": true/false, "ShowExpansionsAsColumn": false, "ShowFolderButton": false, "ShowNotes": false, "ShowEditButtons": false, "ShowFavoriteIcon": true, "NumColumns": 1, "ColumnWidthRatio": [ 0.3333333333333333, 0.3333333333333333, 0.3333333333333333 ] }The idea is to avoid/prevent overwriting factory presets. 
 When preset are saved by user they are always USER presets
- 
 @MikeB Search field and buttons can already be hidden/shown using LAF. But we definitely need some way to disable the user overwriting specific presets. 
- 
 @d-healey 
 You mean "drawPresetBrowserSearchBar".
 I can leave that empty - but the space for the search bar does not disappear.
 At least I have not managed to do that yet
- 
 @MikeB Yeah you're correct. It just makes it invisible but the control is still there. 
- 
 @d-healey 
 Therefore: "Show Searchfield": true/false, :-)
- 
  
- 
 @Tania-Ghosh Wrong Thread,Lol 
- 
 @Natan Oops... 
- 
 @Tania-Ghosh One post per request/bug report so Christoph can track them separately. 
- 
 @Natan Thanks dear. 
- 
 @Tania-Ghosh No Problem  You Mentioned What I Wished You Mentioned What I Wished More Visualization Are Welcome More Visualization Are Welcome





