Perrorist

Turning off the grid definitely helped in seeing the cursor. Thanks.

It could be a size issue. When I select Rectangle and move the cursor over the layer, I have difficulty finding it. (That may be an eyesight issue as well.) In this image, it's in 3 down and 3 across .

It is as I described: a dark crosshair on a dark background. My question is why is it so dark I can't see it. None of the other tools do this.

Definitely the Rectangle Tool.

No, it's not on.

It's an .afphoto file. I've since discovered the problem is that my cursor has changed to a small, dark crosshair that is invisible against a dark blue background. I can't find a Preference option to change that. I'm using Windows 10 Pro on a desktop PC. My normal cursor is a green arrow with a black outline. Just about every other tool is white, so I don't understand why the Rectangle one is different.

I opened a recent file, added a new layer, tried to draw a rectangle, and set the stroke to 1 cm, but the cursor would not appear in the frame. I don't recall having this issue before. Any suggestions.

I can't minimise the screen when it happens, which is annoying.

It's so obvious that I can't believe I missed that. I don't know where the white fill came from. Thanks, both of you.

Thanks for the reply. I've attached the .afphoto file. The answer to your second question is that the rectangles and text were showing before saving but didn't reappear when reloaded. Cookie's room.afphoto

I've not had this issue before. I try to create a rectangle with stroke and fill set in contrasting colours. Nothing appears. Am I overlooking something obvious? (This also applies to text after I've saved the file.)

I let the app detect and install it. There was no description of which privilege it needed.

I got this message updating to 2.0.4 on both Paint and Publisher, but not on Designer. Are those installations still sound? Windows version.

I moved the apps to a preferred drive and created shortcuts. They all looked the same, so I replaced the icons with those from V1 and now it all looks like it should have done from the start. I repeat my comment that the decision to use MSIX and provide no alternative was a bad one and should be reconsidered.

I tried the drag-and-drop idea but it didn't work.