Neue Testversion 24.40b11

[Gerhard Huber]

Hallo,

es gibt wieder eine neue Testversion 24.40b11.

Windows:
https://www.pl32.com/beta/pl2440b11.zip

macOS:
https://www.pl32.com/beta/plx2440b11.zip

Neues:

• PNG-Import: Defekte PNG-Dateien werden besser gelesen
• Farbänderung: Kurveneditor bekommt den Fokus, wenn durch Klicken ins Dokument ein Punkt erzeugt wurde
• Farbänderung: Ein durch Klick ins Dokument erzeugter Punkt kann - wie bei der Gradation - direkt verändert werden
• Diverse Fehlerbehebungen und kleinere Verbesserungen

[shijan]

Some other problems fixed in 24.40b11 added to Large List of Bugfixes 2019-2024:

• Request/Idea: Hide "Close" and "Collapse/Expand" UI buttons from panel tabs to provide more space for tabs and less visual noise in UI.
• Request/Idea: Hue Editor click and drag picker points behave same as currently in Curves.
• macOS Guides became aliased and blurry once i change Guide Color in Preferences->Display->Guides.
• macOS Guides with default color now looks blurry in 24.40b6 macOS
• macOS Guides became aliased and blurry if some Tools are used.
• macOS Rectangle Lasso use additional rectangle frame with handles which looks aliased and blurry.
• Small shift in UI line in Pages list visible only if set list to 32x32 size.
• Levels docking panel can't remember RGB/HIS mode.
• Menu items duplicates in Cliparts, Outlines, Shapes lists.
• Visual artifact when rotate document using mouse cursor.
• Program crash when use Focus Stacking or Stitch.
• In macOS version Backspace key don't works in Text tool. Can't delete typed letters when press Backspace key.
• Can't create Guides if number of guides in dialog window is typed by keyboard.

[Herbert123]

Instant crash bug: when I drag a colour swatch from the color swatches to the document colour swatches panel, PhotoLine crashes.

[Herbert123]

On the Mac Studio at work yesterday I noticed that the guide creator wouldn't create guides. They would appear, but then disappear when I pressed OK.

Not tested with this particular version (only the B10).

[shijan]

Is it my imagination or adjustments in large sized images now works slower than in earlier versions? It also feels slower than usual when i return in History panel or zoom document in/out with mouse wheel.

[der_fotograf]

The overall performance and speed is slower than version 24.01, particularly when resizing images (enlarge). Other than that, I haven't noticed problems – yet…

[Martin Huber]

Instant crash bug: when I drag a colour swatch from the color swatches to the document colour swatches panel, PhotoLine crashes.

and

On the Mac Studio at work yesterday I noticed that the guide creator wouldn't create guides. They would appear, but then disappear when I pressed OK.

Not tested with this particular version (only the B10).

I will fix that.

[Martin Huber]

The overall performance and speed is slower than version 24.01, particularly when resizing images (enlarge). Other than that, I haven't noticed problems – yet…

What do you mean by "resizing images"? Resizing them using the Layer Tool or scaling them by using "Layer > Scale Layer"? Or something different?

[der_fotograf]

Scale Document after I have merged down all layers with an Action:

Screenshot 2024-03-29 at 17.43.29.png

[der_fotograf]

I've measured the time for the scaling process (with an Action).

Image _DSC6422.TIF
Format: 7008x4672x48bit

Action: »Scale Width 120« as follows

Screenshot 2024-03-29 at 19.20.48.png

PL Version 24.01: 3 seconds
PL Version 2440b11: 6 seconds

[Herbert123]

Instant crash bug: when I drag a colour swatch from the color swatches to the document colour swatches panel, PhotoLine crashes.

and

On the Mac Studio at work yesterday I noticed that the guide creator wouldn't create guides. They would appear, but then disappear when I pressed OK.

Not tested with this particular version (only the B10).

I will fix that.

I also noticed that when I drag a document colour swatch to a vector object in the page, it will crash as well.

Thanks for looking into this.

[Herbert123]

A quick request for importing (merging) colour palettes:

When a colour palette is dragged into the Colors panel PhotoLine will REPLACE all the existing entries.

I am building palettes and grouping these, but I have made the stupid mistake of dragging in a palette file and it will then remove all my entries. This has happened to me at least 5 times now...

Yes, I saved prior versions, but sometimes I forget. And I have to start anew for 10 or 15 imports. And with the new grouping functionality this behaviour should REALLY default to MERGE rather than replace!!! It's super-frustrating, and has cost me valuable time.
And it is not possible to undo this.

Very frustrating!

If the default behaviour is set to MERGE it will be possible for the user to delete others.
I have to import many palette files by choosing the "merge" option in the panel context menu - dragging and dropping would be SO much faster too!

Ideally a modifier key would distinguish between the two behaviours:

[1] drag and drop a palette file into the colors panel: MERGE
[2] drag and drop with the CTRL or ALT modifier key pressed: REPLACE

This would also be helpful for other panels such as the gradients, textures and patterns.

Secondly, it would be immensely helpful if we could drag and drop (or use the merge menu option) to import multiple sets in one go. But that is a "nice to have feature". As long as we can drop palette files and merge those instead of replace the existing entries, it will work so much smoother.

Also: the name of that panel "Colors" doesn't suffice anymore to describe that panel now that it is possible to create multiple groups (palettes or palette groups). A group of colours is named a palette or colour set.

A much improved English label would be "Palettes" or "Color Palettes". Or "Color Sets". I prefer "Palettes", though.

[shijan]

Also: the name of that panel "Colors" doesn't suffice anymore to describe that panel now that it is possible to create multiple groups (palettes or palette groups). A group of colours is named a palette or colour set.

A much improved English label would be "Palettes" or "Color Palettes". Or "Color Sets". I prefer "Palettes", though.

I experiment erarlier with renaming of menu items and tabs in PhotoLine.xml, but after some attempts i remain "Colors" name as is.
"Colors" is a short name from "Color List". It fits in global naming logic because other similar pairs look the same:
Brush List - Brush Editor
Curves List - Curve Editor
Line Style List - Line Style Editor
and by same logic: Color List - Color Editor.

ALso there is no any real default name for this definition.
Phostoshop and Affinity use name "Swatches".
Krita use name "Palettes".
macOS and PhotoLine use name "Colors"

[Herbert123]

I feel "palettes" still hits the nail on the head. "Colors" is too generic; better would be "Color Sets" or "Color Palettes" (bit of an open door, though, that last one).

A palette is a collection of colours: it doesn't matter if it there is one palette or multiple defined as groups.

"Colors" just doesn't make a lot of sense to me. It worked somewhat before the introduction of the new grouping option. But no longer a good label in my opinion.

Anyway. It's only a name, I suppose.

In regard to the overall performance: I agree that PhotoLine feels... slower to work with. Even with a simple document zooming in and out is really slow. And selecting an asset in the Cliparts results in a slow response of the PhotoLine window (clicking an asset turns the main window bar white, and then dark again. It takes a second for this to complete. Not sure if that was the case before this version.

But overall things feel slower to respond.

[Herbert123]

The Cliparts panel still is very buggy:

- moving assets between groups or just reordering creates copies.

- group a few items. Then delete the items in this group. An empty group remains, but dragging assets into this empty group doesn't work, and a duplicate is made in the root

- I want to create groups of different page templates for different purposes: DIN paper document templates, texture document templates, screen document templates, and so forth.
I create a new file, and save the PLD. I then add this document file as an asset to the cliparts.

But the icon is empty, because the document is empty. So there is no difference between all these document templates.

- placing/merging PLD files in the cliparts panel does not label those assets. Ideally those would be labelled according to their file name (without the extension).

- placing a PLD that is defined as an A4 document in the cliparts doesn't work properly: it doesn't maintain the document size (imports as an empty square) and guides are not maintained either.

- the Large Text List thumbnail display is still too small. Even Large Mode (thumbs only) is too small depending on the context. It would be great if we could zoom in and out with CTRL-scrollwheel and/or have an option to increase the thumbnails for each display mode.