-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deleting a non-empty recipe folder causes a crash #622
Comments
Thanks for raising this. From a quick check I believe this is fixed by #617 but that fix introduces a related bug that dragging a recipe into a folder does not show up the change in the UI until you restart the program (almost certainly a signals issue that will be a small fix). Once #617 is merged, I will have a look at fixing the drag-and-drop. |
Making progress. Fixed the drag-and-drop, but also confirmed that deleting a non-empty folder does still cause a crash even with the new database layer (#617). At first glance, I think it may be related to the fact that we delete the folder before we delete its contents (in |
There isn't really a folder to delete and nothing is in the folder. The folder is a display layer trick, driven by an attribute on each object. If no object refers to a folder, that folder ceases to exist. It gets tricky with sub-folders. If I were to make a random guess, check the signals being emitted and make sure all of the deletes are done before we finish the remove row operation. |
Thanks for the suggestion, will take a look. |
Stronger typing for BtTreeItem::Type, and fix for Brewtarget/brewtarget#622
I believe this is fixed by the commits above. Please re-open if not. |
If a recipe folder is deleted and there is a recipe in it, Brewtarget crashes with "Segmentation fault (core dumped)". However, the folder can be deleted if all of the recipes are deleted first.
The text was updated successfully, but these errors were encountered: