PDA

View Full Version : Bug Report: AR 5 Crashing when pasting into a Group that's not visible



Pat McDonald
02-27-2018, 11:27 AM
It's so long since I posted a bug report I've forgotten where to post it.

I hope it's OK here.

When I try to paste into a Group that is not visible, AR crashes!

I have the latest version of AR

Windows 10

I have various colour palettes that I keep in a group. Because they can clutter up the canvass I often make the group invisible. Then, if forget and try to paste a new palette into that group (which is invisible) AR crashes.

Unusual combination of circumstances, but ...

Pat

HannahRage
02-27-2018, 11:55 AM
Okay, we need to look into that. I am not getting a crash when I test it here, can you walk me through the exact steps you are taking?

e.g. where are you clicking before pasting? How many layers in your group? How are you copying and pasting? (Selections, shortcuts, menu commands?)

Does it happen with a new test painting, or just the one you are currently working on?

Pat McDonald
02-27-2018, 09:24 PM
Hannah,
Thanks for answering.

The (simple) steps in this case
• Create a Group with the first layer, Layer 1
• Put some Oil paint down
• Copied with the marque selection
• Pasted to Layer 2, no problem.
• Switch off the visibility of the Group and paste exactly the same object to an new layer, Layer 3
• It pastes but warns me that the layer isn’t visible
• When I try to make the Group visible we get the error message I’ve included.
• Pressing OK, or trying to close the MessageBox doesn’t work, nor can I close Artrage normally. I have to close Artrage by Window 10’s Task manager

94730
Puzzling,

Pat

HannahRage
02-28-2018, 12:51 PM
Aha, I can get that now - perfect, thank you!

Pat McDonald
02-28-2018, 09:47 PM
Thanks, Hannah

Bertrude
03-23-2018, 03:10 AM
Just to confirm (and apologies for the bump), but this also happens on the Mac version too.

94873

Pat McDonald
07-06-2018, 11:01 PM
Does 5.0.7 solve this bug?

Pat

markw
07-08-2018, 03:55 AM
Hi Pat and Bertrude,
No this issue’s not fixed yet and it wasn’t mentioned in the fixed list for 5.0.7.

MattRage
07-09-2018, 10:32 AM
It looks like that one got missed as we were working on the update, it's in our list and will be addressed in the next update. Sorry about that!

Pat McDonald
07-13-2018, 04:15 AM
Thanks for letting me know Matt

Pat McDonald
08-25-2018, 01:48 AM
Matt,

I've been away and have just got back to Artrage - and, thank you. Yes, this has solved the issue.

Pat