 DeLargy's Print
DeLargy's Print
    
          
          
        My feedback
1 result found
- 
New document (File > New) window / dialog is blank / black / gray / empty- 
          
            Capture d’écran, le 2021-02-19 à 20.42.23.png 200 KB 
- 
          
            illustrator tech issues - create new.jpg 499 KB 
- 
          
            Screen Shot 2020-07-09 at 06.35.08.png 1059 KB 
- 
          
            Screen Shot 2020-06-28 at 10.00.53 PM.png 359 KB 
- 
          
            Screen Shot 2020-05-29 at 1.39.00 PM.png 2908 KB 
- 
          
            Screen Shot 2020-05-29 at 1.39.00 PM.png 2908 KB 
- 
          
            Screen Shot 2020-03-03 at 12.32.55 PM.png 302 KB 
- 
          
            Screenshot 2019-11-14 at 10.01.55.png 624 KB 
- 
          
            Screenshot 2019-11-14 at 10.05.54.png 174 KB 
- 
          
            Screenshot 2019-11-14 at 10.06.17.png 221 KB 
- 
          
            1.PNG 22 KB 
- 
          
              ice_video_20181212-103345.mp4 2807 KB 
- 
          
            Ai home page.png 81 KB 
- 
          
            newdocument_blackpanel.jpg 133 KB 
- 
          
            Capture_AI.JPG 59 KB 
- 
          
            Illustrator.PNG 125 KB 
- 
          
              IMG_0071.MOV 26874 KB 
- 
          
            Capture.JPG 50 KB 
 75 votesWe are not hearing this anymore in recent times, marking this one as Resolved. If you are still facing this issue, please add a comment. An error occurred while saving the comment DeLargy's Print supported this idea · An error occurred while saving the comment DeLargy's Print commented When I try to create a new document, the panel will not let me input any artboard sizes, quantities, etc. It becomes frozen and I cannot close the panel or make any changes to it, so I have to manually close Illustrator since I can't work on anything while that panel is open. I've tried waiting and nothing changes. It doesn't happen every time but it is getting increasingly common. 
- 
          
            
 
          
@Egor This appears to have fixed the problem after using the legacy version the past two days.