Large List of Bugfixes 2019-2023 (aka Legacy Large List of Suggestions and Requests for Photoline UI and Tools)

[shijan]

Not sure if it possible with current PhotoLine color management engine, but i would like to add request for additional color space transform intent described as "Perceptual appearance". It is used in ArgyllCMS and this intent transforms color spaces in very unique and gentle way.

Here is also full list of ArgyllCMS Rendering intents from DisplayCAL FAQ (many of them are very specific and so i have no idea how to use them in real life):
“Absolute colorimetric” is intended to reproduce colors exactly. Out of gamut colors will be clipped to the closest possible match. The destination whitepoint will be altered to match the source whitepoint if possible, which may get clipped if it is out of gamut.
“Absolute appearance” maps colors from source to destination, trying to match the appearance of colors as closely as possible, but may not exactly map the whitepoint. Out of gamut colors will be clipped to the closest possible match.
“Absolute colorimetric with white point scaling” behaves almost exactly like “Absolute colorimetric”, but will scale the source colorspace down to make sure the source whitepoint isn't clipped.
“Luminance matched appearance” linearly compresses or expands the luminance axis from white to black to match the source to the destination space, while not otherwise altering the gamut, clipping any out of gamut colors to the closest match. The destination whitepoint is not altered to match the source whitepoint.
“Perceptual” uses three-dimensional compression to make the source gamut fit within the destination gamut. As much as possible, clipping is avoided, hues and the overall appearance is maintained. The destination whitepoint is not altered to match the source whitepoint. This intent is useful if the destination gamut is smaller than the source gamut.
“Perceptual appearance” uses three-dimensional compression to make the source gamut fit within the destination gamut. As much as possible, clipping is avoided, hues and the overall appearance is maintained. The destination whitepoint is altered to match the source whitepoint. This intent is useful if the destination gamut is smaller than the source gamut.
“Luminance preserving perceptual” (ArgyllCMS 1.8.3+) uses compression to make the source gamut fit within the destination gamut, but very heavily weights the preservation of the luminance value of the source, which will compromise the preservation of saturation. No contrast enhancement is used if the dynamic range is reduced. This intent may be of use where preserving the tonal distinctions in images is more important than maintaining overall colorfulness or contrast.
“Preserve saturation” uses three-dimensional compression and expansion to try and make the source gamut match the destination gamut, and also favours higher saturation over hue or lightness preservation. The destination whitepoint is not altered to match the source whitepoint.
“Relative colorimetric” is intended to reproduce colors exactly, but relative to the destination whitepoint which will not be altered to match the source whitepoint. Out of gamut colors will be clipped to the closest possible match. This intent is useful if you have calibrated a display to a custom whitepoint that you want to keep.
“Saturation” uses the same basic gamut mapping as “Preserve saturation”, but increases saturation slightly in highly saturated areas of the gamut.

[shijan]

Mac specific Request: option in preferences to use green window button as "Maximize Window" instead of "Fullscreen".
This is similar to Photoshop, and many other professional apps that mostly require quick fit window to screen instead of switch to fullscreen mode. Currently in PhotoLine there are a lot of quick options to switch to Fullscreen mode (hotkey, custom toolbar icon, mouse click to green window button) but only one rather complicated option to maximize window (Alt+mouse click to green button) There is also option to double-click hand tool, but it problematic because it maximize window only to the right and bottom directions.

[shijan]

...

[Herbert123]

Suggestion to remove legacy gradient background from color puppet info panels:

Current:


Suggested:

Expanding on this: I would also prefer blue tinted selected layers in the layer panel instead of the grey ones. Blue-->selection. Consistent with other image editors as well.

[Gerhard Huber]

Expanding on this: I would also prefer blue tinted selected layers in the layer panel instead of the grey ones. Blue-->selection. Consistent with other image editors as well.

We have this problem here periodically, so once more:
- selections are colored in PhotoLine and every consistent software, when they have a focus
- selections are grey when they have no focus

The layer panel is a problem, because all want to have colored selections but no focus.
By default, the layer panel looses the focus automatically after every operation to get the next key stroke, or what ever, to the document and therefore the selection will be grey.
You can change this setting at "Options > Working > Special > Layerlist with keyboard support".
But you won't be happy with it.

[Herbert123]

Expanding on this: I would also prefer blue tinted selected layers in the layer panel instead of the grey ones. Blue-->selection. Consistent with other image editors as well.

We have this problem here periodically, so once more:
- selections are colored in PhotoLine and every consistent software, when they have a focus
- selections are grey when they have no focus

The layer panel is a problem, because all want to have colored selections but no focus.
By default, the layer panel looses the focus automatically after every operation to get the next key stroke, or what ever, to the document and therefore the selection will be grey.
You can change this setting at "Options > Working > Special > Layerlist with keyboard support".
But you won't be happy with it.

? Most graphics/design related software highlight layers in a layers panel with a blue tint no matter whether the layer panel has focus or not: Krita, Blender, PS, Xara, Affinity, Pro Motion NG, ClipStudio Paint, Illustrator, Pixelmator, Corel Draw, Corel PaintShop Pro, and others...

For some reason only know to open source developers, InkScape and Scribus behave the same as PhotoLine when "Layerlist with keyboard support" is turned on.

While I (sort-of) understand the logic behind the "layerlist with keyboard support" behaviour, the only thing I would like is that when this option is turned off, the layer selection colours used for selected layers in the layers panel are the same blue ones as when the layer panel is focused with that option turned on. Instead of the grey values, which just don't look that good and lack the visual cue / understanding as the colour blue (which is generally understood as a selection related colour). It would then be in line with most other graphic software.

Even more so since keyboard based layer navigation can be enabled via the Layer-->Navigation options.

Best would be to allow the user to configure the layer selection colour when that layerlist option is turned off.

[PhilM]

Instead of the grey values, which just don't look that good and lack the visual cue / understanding as the colour blue (which is generally understood as a selection related colour). It would then be in line with most other graphic software.

+1

Philippe

[bkh]

Not sure if it possible with current PhotoLine color management engine, but i would like to add request for additional color space transform intent described as "Perceptual appearance". It is used in ArgyllCMS and this intent transforms color spaces in very unique and gentle way.

Seems you misunderstood something here – ArgyllCMS is for creating profiles, and the variants you mention are the different possibilities to specify how "perceptual" and "saturation" will behave when a CM engine uses the transform. In other words, once a profile is created, the meaning of "perceptual" and "saturation" is hard baked into the profile, and ICC profiles only allow for three transforms, one being "colorimetric". Every CM engine (including the ones supported by PL) is supposed to follow what's specified in the profile.

If you want all the options ArgyllCMS offers, the only possibility is to create different profiles and to set the corresponding profiles in PL as required.

Cheers

Burkhard

[shijan]

Seems you misunderstood something here – ArgyllCMS is for creating profiles, and the variants you mention are the different possibilities to specify how "perceptual" and "saturation" will behave when a CM engine uses the transform. In other words, once a profile is created, the meaning of "perceptual" and "saturation" is hard baked into the profile, and ICC profiles only allow for three transforms, one being "colorimetric". Every CM engine (including the ones supported by PL) is supposed to follow what's specified in the profile.

Yes, ArgyllCMS is for creating profiles, but it also can transform profiles similar to color management engines. I just show it as example.
PhotoLine CM engine already can do some different types of transforms between input/document/output profiles, so why don't add perceptual appearance to it as well?
Nothing is hard baked if you do color management in Document mode (see my investigation about color management here viewtopic.php?f=1&t=6279&p=46973#p46875
Currently i can transform from one profile to another with with perceptual appearance intent by creating 3D LUT in DisplayCAL. Those LUTs works very well in PhotoLine instead native color management.
Please correct me if i wrong.

[shijan]

...

[bkh]

Nothing is hard baked if you do color management in Document mode

The transformation rules are hard baked into the colour profiles (three variants, see my original post).

Currently i can transform from one profile to another with with perceptual appearance intent by creating 3D LUT in DisplayCAL. Those LUTs works very well in PhotoLine instead native color management.

That‘s just what I wrote. You just can‘t have more than one perceptual intent in one profile.

Cheers, Burkhard

[shijan]

Extend Transform arrow handle active area to all object edges instead of single point in the middle of each edge.
Use more user friendly, position dependent transform/rotate handle cursors.
Example:

[shijan]

...

[shijan]

Option to autohide handles during object movement.
Example:

[shijan]

...