Factory vs. User Presets

[MikeB]

@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?

[ustk]

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...

[d.healey]

What happens if you make the preset files themselves read only?

[marcLab]

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.

[d.healey]

@marcLab That's a clever idea. Can you change the hidden state of the button dynamically?

[MikeB]

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.

[MikeB]

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

[d.healey]

@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.

[MikeB]

@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

[d.healey]

@MikeB Yeah you're correct. It just makes it invisible but the control is still there.

[MikeB]

@d-healey
Therefore: "Show Searchfield": true/false, :-)

[Tania Ghosh]

[Natan]

@Tania-Ghosh Wrong Thread,Lol

[Tania Ghosh]

@Natan Oops...

[d.healey]

@Tania-Ghosh One post per request/bug report so Christoph can track them separately.

[Tania Ghosh]

@Natan Thanks dear.

[Natan]

@Tania-Ghosh No Problem You Mentioned What I Wished More Visualization Are Welcome

[marcLab]

@d-healey If we can't do it dynamically with Content.setPropertiesFromJSON, then you can always put a panel over it (Save Preset) and play with "visible" true/false to hide the panel. It's a bit sketchy. But it's an idea.