Lucky Clan Forum

Support => Suggestions, Ideas, Bugs => Topic started by: Andych56 on June 06, 2019, 08:20:45 PM

Title: Elastify tool bug
Post by: Andych56 on June 06, 2019, 08:20:45 PM
I'm not sure if anyone else has seen this and reported it.
When using the Elastify tool for more than 3 mins or so it stops working. I'm unable to paint any strokes and have to either apply or cancel out of the Elastify function.
Maybe this has already been flagged for the big update that is coming?
Title: Re: Elastify tool bug
Post by: Bulotron on June 09, 2019, 11:47:19 AM
Also there is another problem when accessing the elastify in the fullscreen mode it’s impossible to see any of the toolbars of elastify therefore unable to accept or exit.
Title: Re: Elastify tool bug
Post by: Lucky Clan on June 13, 2019, 07:33:39 AM
It will be fixed in the next minor update
Title: Re: Elastify tool bug
Post by: Lucky Clan on June 13, 2019, 08:14:16 AM
I'm not sure if anyone else has seen this and reported it.
When using the Elastify tool for more than 3 mins or so it stops working. I'm unable to paint any strokes and have to either apply or cancel out of the Elastify function.
Maybe this has already been flagged for the big update that is coming?

I cannot reproduce this problem, could you give me more details? Please use Artstudio>Send Feedback option in Artstudio Pro app to send me some details about your iPad.
Title: Re: Elastify tool bug
Post by: Andych56 on June 13, 2019, 08:23:53 AM
Ok no probs, I just sent it through to you.
iPad sketchpad is the name of my iPad so you know it’s from me.
Title: Re: Elastify tool bug
Post by: SebLiese on June 19, 2019, 02:36:40 PM
I think this has to do with accidently touching the screen with your hand/finger at the wrong time. I often end up seemingly unable to elastify further. But then when you press a combination of undo,redo and the little preview button, it usually goes back to normal.
Title: Re: Elastify tool bug
Post by: Andych56 on June 19, 2019, 07:27:11 PM
Ok great thanks I’ll give that a try.
It’s good to know it’s a bug and I’m not the only one having this problem.