PrismLauncher
Add a lock update icon
this is continuation of #3248
so here is the text from there:
fixes #83 fixes #440 fixes #1066 closes #764 fixes #1424(by the fact that the lock will be enabled) regarding #764 I do not feel like it would be useful for the user to lock Remove, Enable, and Disable options (but if you consider it is a needed thing then I will leave the issue open) This only works with managed resources because I do not want to create an additional to maintain alongside the current packwizz. Also, why would you disable updates for mods with no meta? This should work for all resources. Based on #1079
Now there is no checkbox but an actual icon to signal if is locked or not. Also please suggest places from where I can take the two icons to add them in each respective theme folder.
What I meant was to display a lock icon on the name column if it's not interactable. Having it on a separate column does make it feel like it really should be. (though I guess we also display the warning icon there :( )
Huh, this is strange. On some of my instances it is interactable. On other's not.
I need it to be on a separate column so I do not need to hack my way up to determine if the icon was pressed or not. This should always be interactable. Did not add code that would block it. Are those instances custom or downloaded from Cursefore/Modrinth?
On some (initially all) of my existing instances the update column is missing the separator line and can't be moved
The selection also doesn't cover the lock
Easier to see if you remove the background
On these instances the update toggle won't work.
I'm not overriding column visibility yet this still seems to only happen for some instances and it also randomly stopped happening from some of them.
It is an issue with column stuff: sometimes, when we add a new column, the column is displayed to the user for some time, but it is not interactive. Right-click the header and toggle the column visibility in this case. This was not introduced in this PR, and it usually fixes itself after you reopen the edit instance. You can see similar behaviour in the track dependencies PR with the required by and requires columns