Jump to content
You must now use your email address to sign in [click for more info] ×

Publisher 2.2.0, Windows: field panel bugs still not fixed


4dimage

Recommended Posts

Hi, as reported here:

 

As feared, some bugs that where already logged in the Windows version in the beta were not fixed in the "stable" release v2.2.0.

When I see the advertisement for the new release on the Serif website, the MAC dialog seems to be shown there. This also looks like it's working properly. Can any MAC user confirm this ?

I increasingly have the feeling that some UX errors and weaknesses will be fixed for the MAC/iPad version with high priority and then in the end there will be no time left to implement them identically in the Windows version ?!

image.png.142941861b5592d5ff6fae5910d81623.png

 

And this is how the bugs in the current v2.2.0 Windows release still look like:

Flipping form groups, missing/different translation, wrong button labels ?!?!

 

image.png.88d89c8621bba3542c3ac41ca1477258.png

 

Not funny...

 

Hardware: Windows 11 Pro (23H2, build 22631.3447, Windows Feature Experience Pack 1000.22688.1000.0), Intel(R) Core(TM) i9-14900K @3.20 GHz, 64 GB RAM, NVIDIA RTX A4000 (16GB VRAM, driver 551.61), 1TB + 2TB SSD. 1 Display set to native 2560 x 1440.
Software: Affinity v1 - Designer/Publisher/Photo (1.10.6.1665), Affinity v2 (universal license) - Designer/Publisher/Photo, v2 betas.

Link to comment
Share on other sites

  • Staff

Sorry, but the issues you reported have not yet been fixed. There is no need to make a second thread for issues that are already acknowledged.

If your issues were addressed the "Serif Info Bot" would have posted to your beta thread to say they were fixed, and as that has not happened, you can tell that those issues are still outstanding.

Is there anything in your post above that represents a new bug that also needs reporting in addition to your earlier post?

Patrick Connor
Serif Europe Ltd

"There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self."  W. L. Sheldon

 

Link to comment
Share on other sites

  • Staff

I have looked into your original report, and these bugs were reported quite late in the 2.2.0 beta cycle (2 of them during the first Release Candidate 2.2.0.1986) Once Serif Development Beta cycles enter Release Candidate phase, from then on  only high severity or very very safe fixes make it into the software. This is to avoid last minute regressions. Consequently although they have actually been addressed already those fixes did not make it into 2.2.0 and so will be tested as part of the next customer beta cycle.

Patrick Connor
Serif Europe Ltd

"There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self."  W. L. Sheldon

 

Link to comment
Share on other sites

  • 4 weeks later...
  • Staff

The issue "[Win] Tooltip for Add Custom Field in Fields Panel missing in 1971 Windows" (REF: AF-15) has been fixed by the developers in internal build "2.3.0.2083".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

Link to comment
Share on other sites

  • Staff

The issue "[Win] Tooltip for Create Custom Field is incorrect after deleting Custom fields" (REF: AF-17) has been fixed by the developers in internal build "2.3.0.2083".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

Link to comment
Share on other sites

  • Staff

The issue "Tooltip for Create Custom Field shows as Default Format when no document is open" (REF: AF-16) has been fixed by the developers in internal build "2.3.0.2083".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.