Is there a way to recover from the file crashing when I accidentally select a point that was not created in the right point in history?
crashing regularly now.
tomomi pants.sm2d (26.5 KB) tomomi.smis (987 Bytes)
2 Likes
Sometimes the computer remembers the error after the pattern has been closed and reopened. In this case it is best to shutdown your computer, wait a while and then restart it. Open the pattern and check if the error is still there. I suspect that this may be the case because I opened your pattern and it didn’t show any problems.
1 Like
Opens fine for me… other than the image it was trying to import.
I would just close any running Seamly2D processes… on Windows that sometimes requires opening Task Manager to stop a Seamly2D that’s hung in the background. Restart the app and don’t load any autosave file if it’s trying to do so.
2 Likes
Hi @emilyli - Are you still having this problem?
1 Like
yes. and it doesn’t seem like it’s always a history problem.
for example I just picked A72 and got this error.
when it crashes and i close and reopen it allows me to pick the point.
-
lilimade pants.sm2d (36.9 KB)
-
janna.smis (986 Bytes)
1 Like
@emily, thanks for posting!
For some reason the 1st & last images above are not displaying, but if you click on them they open and display properly.
I am opening a ticket with Discourse, we’ll see if this can be solved.
2 Likes
still having this problem. with a new file.
when i pick point A50.
julie.smis (985 Bytes)
julie pants.sm2d (16.7 KB)
1 Like
It took me a little bit to backtrack through the pattern to realize that point A50 was inserted earlier in the history… but is what you were trying to do?
As I’m not having a problem clicking A50. ??
I should note that I discovered a bug (unrelated?) in regards to not having the image files, where I and just skipped loading them… adding any tool then crashed the app.
1 Like
if i click on point a50 right after i add it earlier in history it crashes. if i save right after and close it and reopen it allows me to pick a50.
2 Likes
Right. You have to move the pointer back to the end of the History after you insert a tool. It’s why you have to be careful when inserting tools earlier in the History.
3 Likes
Yeah the History tool UX is a bit rough. There are zero instructions. Users discover how to use it properly through by trial-by-error.
1 Like
I played around with having the pointer automatically return to the end of the list, but it’s tricky as it’s wrapped up in several layers of signals between the tool and mainwindow and the non modal History dialog. I had it working some of the time, but not always. I’ll have to look at that branch again at some point, and see if it makes more sense after setting it down for a bit.
2 Likes
Instructions at the bottom of the dialog box would be nice… When it first opens display “Search for object to find insertion point. New object will be inserted after the searched object.” After insertion display “Move arrow to bottom of list and save file.” When arrow is at bottom of list enable a Close button. The Cancel button is always enabled.
3 Likes
Should also say USE WITH CARE. 
2 Likes
There is a Close button… it says OK. Personally I’m not a fan of using Ok, when there’s another button that describes the action better… like Save, Close, Cancel, Apply, Yes or No. Ok is like shrugging one’s shoulders… Ok - whatever. 
The behavior the History should have is when the dialog is closed - clicking OK or the Window close button… the pointer should reset. That’s what I was working on, and got it to work in most cases, but not all.
Again you have to remember the History is a non modal dialog, and doesn’t have to close. You could insert a tool, minimize, forget to move the pointer, and now all the new tools are being inserted instead of appended - which is no bueno.
Maybe the behavior should be something like this… first change the OK (regardless) to Close. Then have the dialog go into an insert mode where Close and Minimized is disabled when the pointer is moved from the end of the list, where an OK button is added. Clicking OK ends the insert mode, and returns the pointer to the end, and Close and Minimized is re-enabled.
2 Likes
I’m a little worried about what if one of the linux users whose OS is set to lock sub windows to their primaries tries to use it & can’t because the window is locked in the way.
Also, it’s probably been brought up before, so I’m assuming it’s not an easy fix, but don’t want to leave it at assumptions, while playing with History in order to be more sure of the context here, I managed to crash Seamly several times, & wonder if it would be reasonable to make it so that clicking on a future node will automatically reset History to the present.
The easy thing to do is just allow inserting 1 tool at a time and have it reset the pointer after the inserted tool is created to the last row +1, instead the current row +1. That way the state of the dialog is moot, and the History will always be set to append, unless a user is intentionally inserting 1 tool. Besides - To be honest - if you have to insert a bunch of points or lines, you probably need to redo the pattern.