If an anchor point is selected, ‘join’ curves doesn’t work

[iuli]

As stated above; video proof below.

Hopefully we won’t have to wait months for such an important bug to be addressed. It works if you deselect the point, but that’s terribly tedious and it’s not a workaround, when ‘join curves’ is a fundamental part of your work.

Unrelated to this, a couple of weeks back I’ve lost thousands of designs saved as assets, (while saving a design in ‘assets’ the app crashed and everything in assets has gone, without the rest of the app to be affected), some of them for good; the state Affinity Designer for IPad is, two years later, is disappointing to say the least. I didn’t have unreasonable expectations, but not this terrible level of updates’ support either.

Kind regards 

[walt.farrell]

3 hours ago, iuli84 said:

Unrelated to this, a couple of weeks back I’ve lost thousands of designs saved as assets, (while saving a design in ‘assets’ the app crashed and everything in assets has gone,

As it's unrelated, you should make a separate topic for that, to help Serif track it reliably.

Assets are stored in a single file, which means that any failure while writing the file is likely to lose all of them. At this point, given that architecture, it's important to have good system backups so you can recover from such errors by restoring the old version of the file. That avoids major data loss.

[iuli]

3 hours ago, walt.farrell said:

As it's unrelated, you should make a separate topic for that, to help Serif track it reliably.

Assets are stored in a single file, which means that any failure while writing the file is likely to lose all of them. At this point, given that architecture, it's important to have good system backups so you can recover from such errors by restoring the old version of the file. That avoids major data loss.

Thank you for your reply; you, Alfred and a couple more great people here always come with valuable advices and I admit many times I’ve found eloquent responses to my own questions, without even having to ask them.

Now, I didn’t want to start another topic because I didn’t want to put my cheap outrage here in these fantastic forums; but I still miss complex character designs for a project; I’m aware of my own stupidity of not doing backups to my files, but it didn’t crossed my mind for a second I need to save anything when comes to assets, because in two years never happened to me; how could something like this happen anyway? Why a broken program passed the most rudimentary stages of development if things like this are bound to happen for an ecosystem the recovery of your hard work is impossible? 

So while having myself to blame, that doesn’t make AD less faulty with their lack of auto-save functionality which (alongside with not being able to import swatches) — which really in my eyes makes it far less evolved than I’ve thought two years ago when I started using it (and wasting, over time,  thousands of hours to accommodate to a new software — and I’m saying ‘wasting’ because my trust is slowly slipping out; I’m using more and more a new program now, which paradoxically for its free status receives tens of more valuable updates than AD; I’ve always said the price wasn’t my motive of using AD but it’s functionality, I wanted to believe the support it will be much more higher than we see now, without glitches that ruin tens of hours of your own hard work.  I’m getting mad only by thinking of it; I wouldn’t mind paying a monthly subscription for AD, I’ve said this from the start, its cheap price compared to other software matters little when you tailor your whole working life around a program for two years, just to find out it’s broken, it has bugs that ruins your life... see that’s why I didn’t start a new topic about a issue no one could help you with (except advices that, although nice and welcomed, I’m well aware of).

I remember asking that night on a topic about someone loosing his files, in AD for windows forums, and the lack of response was to be expected since there really could be no one able to help; the iOS terrible architecture is to blame too, of course — more reason for AD to become a reliable software and not this one, where you can find yourself loosing projects for good.

Anyway — thanks again for your reply; you’re nice and you try to be helpful as always

Kind regards 

[Alfred]

4 minutes ago, iuli84 said:

Thank you for your reply; you, Alfred and a couple more great people here always come with valuable advices and I admit many times I’ve found eloquent responses to my own questions, without even having to ask them.

Thank you for your appreciative comment.

I can confirm the ‘Join Curves’ bug that you’ve reported here.

[Gabe]

Hi all,

This is not a bug I'm afraid . To join 2 curves, you either need tot elect the curves and they will join the 2 closest nodes, or you need to select an end node of each curve. When you only have one node selected, there is no other node to join it to, so it's expected is does nothing. 

[DM1]

23 minutes ago, Gabe said:

there is no other node to join it to,

I think the confusion arises because the nodes snap together, giving impression they are now 'selected'. The top nodes shows selected, the node beneath can’t be seen.

It seems strange though that we have both 'Close' and 'Join', where Close doesn’t need the end nodes selected but Join does, even when two nodes are snapped together.