You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I often delete a part of the sheet because I've built that part and will not touch it until the next tech.
The problem is that deleting requires two steps: deleting the row with the recipe, and then unlinking the item, so it stops being red.
My idea is to automatically unlink the item in a row if it was not linked to anything else.
For more clarity, here's an example from pY:
I build the production of Automation Science. I'm done with the stone, so I delete the part that produces stone. However, the stone icon is still red because the stone is now linked but the demand is not satisfied. Therefore, I have to unlink it. (I want to get rid of the part written in italic)
What do you guys think? Maybe I'm wrong, and the still-linked behavior is preferable later?
The text was updated successfully, but these errors were encountered:
I'm mixed here. More often than not, the missing link warning shows me i removed the wrong recipe. But then there's also that case where i did remove the right recipe and want to link to go with it.
I often delete a part of the sheet because I've built that part and will not touch it until the next tech.
The problem is that deleting requires two steps: deleting the row with the recipe, and then unlinking the item, so it stops being red.
My idea is to automatically unlink the item in a row if it was not linked to anything else.
For more clarity, here's an example from pY:
I build the production of Automation Science. I'm done with the stone, so I delete the part that produces stone. However, the stone icon is still red because the stone is now linked but the demand is not satisfied. Therefore, I have to unlink it. (I want to get rid of the part written in italic)
What do you guys think? Maybe I'm wrong, and the still-linked behavior is preferable later?
The text was updated successfully, but these errors were encountered: