John Swistak
My feedback
4 results found
-
[macOS Sonoma]White Screen on drawing marquee/highlighting text in CPU and Overprint Preview modes
-
Screenshot 2023-11-27 at 12.22.58 PM.JPG 449 KB -
Screenshot 2023-11-27 at 12.22.49 PM.JPG 244 KB -
WhatsApp Video 2023-11-16 at 15.41.24.mp4 3953 KB -
Document White Out Issue.png 204 KB -
Screenshot 2023-10-21 at 1.29.41 PM.png 457 KB -
Screenshot 2023-10-21 at 1.28.37 PM.png 558 KB -
problema ao varrer com mouse.mov 8944 KB -
Bildschirmaufnahme 2023-10-04 um 07.20.52.mov 8674 KB -
Screen Recording 2023-10-02 at 16.33.48.mov 28320 KB -
Screen Recording 2023-09-27 at 1.52.40 PM.mov 1406 KB -
Enregistrement de l’écran 2023-09-27 à 09.37.35.mov 6228 KB
75 votesAn error occurred while saving the comment John Swistak supported this idea ·
-
-
14 votes
John Swistak supported this idea ·
-
11 votes
John Swistak supported this idea ·
-
42 votes
The fix of the issue is now available in the latest InDesign 2024(v19.0.1.205). We recommend you upgrade to the latest version for the fix.
If you are unable to see the update, go to the Creative Cloud application and click on the context menu on the top right and click on Check for App Updates.
—
Adobe InDesign Team
An error occurred while saving the comment John Swistak commented
Same problem, wiped all preferences and workspaces in 2024, reinstalled 2023 and they work fine there
John Swistak supported this idea ·
Mac mini 2023 M2 Pro, 32GB, Sonoma
Machine # 1 ID 2024 started using immediately had issues with White Screen on drawing marquee/highlighting text.
Machine # 2 ID 2024 installed but never opened, used ID 2023 everything works fine. No issues.
Opened ID 2024 immediately had issues with White Screen on drawing marquee/highlighting text on both ID 2023 & ID 2024.
So the issue does not start until you START 2024 for the first time, if you downloaded ID 2024 and have not started it ID 2023 will work fine. But once you start ID 2024 you can not undo what ever the problem is even if you uninstall ID 2024 and ID 2023 and just reinstall ID 2023 the problem still persists.
Both identical Macs.
Non of the listed work arounds worked.