- Joined
- Mar 23, 2018
- Messages
- 1,116
- Reaction score
- 2,170
- Points
- 113
I thought it was about time I tidied up my recipe list and I created a few new Folders.
I had quite a few recipes in the DEFAULT folder so I moved them into my newly created folders thus leaving my DEFAULT folder empty - so far so good....
After some other sorting out I decided to return my latest recipe back to the DEFAULT folder - as it seems to be the initial position when selecting to view your [MY RECIPES] button from the menu - so I can always jump back to my latest project.
So, selecting the recipe I want to move back to DEFAULT I hit the [MOVE RECIPES] and select DEFAULT from the drop-down list, (This is in light grey font so it should have told me something!) and... Nothing. Well not quite nothing.
The Recipe was moved right enough but NOT in the DEFAULT folder - that remains empty. The recipe gets moved into a new System generated folder called UNDEFINED (1). Sure enough - there it is.
Let's try again... Select the recipe (in UNDEFINED) and try and move it into DEFAULT...
A new UNDEFINED folder is created with the moved recipe in it. (Or is it? - too many UNDEFINED folders to tell for sure).
The upshot of all this is:
1) Once recipes are moved completely out of DEFAULT (so that it is now empty) they can not be returned. I didn't think about returning one if DEFAULT is still populated so I don't know the consequence of that.
2) Successive attempts to return files into an empty DEFAULT folder creates new UNDEFINED folders - so folder names are NOT unique and could lead to some confusion and the deletion of the wrong folder - if you are not careful.
Can we make it so DEFAULT folder can be written to - it doesn't have to be renamed (editable) like other folders?
Can we make folder names unique - thus avoiding potential deletion disasters?
I'll apologise now for the extra work caused...
I had quite a few recipes in the DEFAULT folder so I moved them into my newly created folders thus leaving my DEFAULT folder empty - so far so good....
After some other sorting out I decided to return my latest recipe back to the DEFAULT folder - as it seems to be the initial position when selecting to view your [MY RECIPES] button from the menu - so I can always jump back to my latest project.
So, selecting the recipe I want to move back to DEFAULT I hit the [MOVE RECIPES] and select DEFAULT from the drop-down list, (This is in light grey font so it should have told me something!) and... Nothing. Well not quite nothing.
The Recipe was moved right enough but NOT in the DEFAULT folder - that remains empty. The recipe gets moved into a new System generated folder called UNDEFINED (1). Sure enough - there it is.
Let's try again... Select the recipe (in UNDEFINED) and try and move it into DEFAULT...
A new UNDEFINED folder is created with the moved recipe in it. (Or is it? - too many UNDEFINED folders to tell for sure).
The upshot of all this is:
1) Once recipes are moved completely out of DEFAULT (so that it is now empty) they can not be returned. I didn't think about returning one if DEFAULT is still populated so I don't know the consequence of that.
2) Successive attempts to return files into an empty DEFAULT folder creates new UNDEFINED folders - so folder names are NOT unique and could lead to some confusion and the deletion of the wrong folder - if you are not careful.
Can we make it so DEFAULT folder can be written to - it doesn't have to be renamed (editable) like other folders?
Can we make folder names unique - thus avoiding potential deletion disasters?
I'll apologise now for the extra work caused...