|
|
Unable to reproduce. |
|
|
i can reproduce strange things with 'manage colors and fills' in scribus 1.5.3 under mac os 10.11.6 – but not exactly the same as christoph under windows: when i open the color editor, all the upper buttons are grayed out. (even 'add' and 'import') – but after clicking on a color entry, most of the buttons become selectable, just 'import' remains grayed out (and doesn't work). |
|
|
colours-fills-153-win10.png (16,680 bytes) |
|
|
Jean: This is what I get with 1.53svn on Windows 10 with no document open. |
|
|
utnik: I already filed another bug for this issue. |
|
|
>> With no document open, the option "Remove Unused" in the "Colours & Fills" dialog is rightfully greyed out in the Linux version of 1.5.3svn In fact after more investigation, the behavior on Windows is the correct one. If you get this behavior on Linux, it means you probably still have old preferences data pre-dating the scribus/user swatches split: the default colorset was referenced by name before, now Scribus uses full disk path. On a fresh OpenSuse Leap 42.2 install, I get the same behavior than on Windows after fixing my prefs on Windows, ie reselecting explictly my default set in color manager. |
|
|
No, I didn't have old preferences active on Linux. Also, the behaviour on Windows is *not* correct. "Remove Unused" refers to colours used in a document. With no document open there can be no "used" or "unused" colours. Likewise, "Delete" doesn't make sense with a protected palette. |
|
|
>> Remove Unused" refers to colours used in a document. False, it also refers to colors used by gradients when no documents is opened. Because you can now define gradients with no document open. >> Likewise, "Delete" doesn't make sense with a protected palette. No, this is where "user" palettes enter in actions. Modified palette will be saved in "user palettes" directory. A user can hence delete colors, keep the colors he needs, without modifying the original palette. Palette locking also depends if a specific file is writeable or not. So you'll have differences of behavior depending on file system, current user rights, and scribus install location. |
|
|
>>False, it also refers to colors used by gradients when no documents is opened. Because you can now define gradients with no document open. Gradients and fill colours aren't identical. Locked colour palettes shouldn't provide an option to delete colours. Moreover, I still insist that "Remove Unused" should be grayed out, because with no document open, there no no way to determine any kind of usage. >>No, this is where "user" palettes enter in actions. Modified palette will be saved in "user palettes" directory. A user can hence delete colors, keep the colors he needs, without modifying the original palette. Palette locking also depends if a specific file is writeable or not. So you'll have differences of behavior depending on file system, current user rights, and scribus install location. You're right here, but there is no way a user can determine what is what, because there's no visual feedback. It all happens in the background. |
- Anonymous
