GRAFKOM Posted March 27, 2020 Posted March 27, 2020 Nobody writes about it?There is a corrupt bleed in the new document. Objects are not displayed even though bleed is running. You have to turn off bleed and turn it back on to display objects. Also when removing elements from Assets, the visibility of objects in bleed disappears. This needs to be fixed before the final release 1.8.3.
Staff Patrick Connor Posted March 27, 2020 Staff Posted March 27, 2020 2 hours ago, GRAFKOM said: This needs to be fixed before the final release 1.8.3. There will be other patches. 1.8.3 is dealing with a serious regression and won't be delayed for things that would need more careful consideration how to address. Frozen Death Knight 1 Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon
GRAFKOM Posted March 28, 2020 Author Posted March 28, 2020 I am writing to clarify. I don't mean bleed in artboards, which has always been broken, but bleed in a normal document. The video presents the problem. Mithferion and Patrick Connor 2
Staff Sean P Posted March 30, 2020 Staff Posted March 30, 2020 HI Grafkom, Thanks for letting us know - it seems to be the action of dragging an item from the Asset Panel that is causing the bleed to turn off. I've reproduced it here, and will get it passed on to development. It was also an issue in 1.7.3 Patrick Connor 1
GRAFKOM Posted April 1, 2020 Author Posted April 1, 2020 OKAY. Still not fixed in the latest version Beta 1.8.3.641
Staff Patrick Connor Posted April 1, 2020 Staff Posted April 1, 2020 On 3/27/2020 at 11:48 PM, Patrick Connor said: 1.8.3 is dealing with a serious regression and won't be delayed for things that would need more careful consideration how to address. It was not mentioned in the patch release notes, so it was not addressed. To all: Please do not bump threads saying "this is not fixed" as it is not a good use of staff time to check threads that have no new information or real change. Move Along People 1 Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon
Joachim_L Posted April 1, 2020 Posted April 1, 2020 3 minutes ago, Patrick Connor said: To all: Please do not bump threads saying "this is not fixed" as it is not a good use of staff time to check threads that have no new information or real change. It is not up to me to tell you how to handle feature requests, bugs, issues etc., but to avoid - as you say unnecessary bumps - you should consider a bug tracking system where the users could look (only view rights if you like) at. You attach tags to the threads, but they do not mean a thing to us. Just a thought. Frozen Death Knight and Patrick Connor 2 ------ Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed
Staff Patrick Connor Posted April 1, 2020 Staff Posted April 1, 2020 These forums work quite well, but having a single place where bugs could be tracked would clearly improve the experience. We have looked into ones that plug into (work with) these forums but as yet have not found one that does what we want. We do not want an independent bug tracking system that requires another account to be created, so one that uses this forums login is a prerequisite. Also this is something that has to work for our whole development department, which does not add to our workload. A_B_C and Frozen Death Knight 2 Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon
walt.farrell Posted April 1, 2020 Posted April 1, 2020 3 hours ago, Joachim_L said: You attach tags to the threads, but they do not mean a thing to us. Also, only a small number of bug-related topics are tagged with a bug identifier, so there's no good way to tell from the release notes which ones Serif thinks they have addressed. -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
GRAFKOM Posted July 30, 2020 Author Posted July 30, 2020 I can shyly say that in the Designer Beta version - 1.8.4.693, the bug is still unrepaired.
Recommended Posts