Open GoogleCodeExporter opened 9 years ago
This is somewhat of a chicken and egg problem. Missing mechanic files is an
unknown unknown, and one can't reasonably code for that.
I'll be happy to accept a patch request, with tests, if the algorithm is right.
Original comment by konigsb...@gmail.com
on 13 Sep 2012 at 8:10
Sorry I don't understand. Why can't we just check if a directory is empty?
Original comment by sebidiet...@gmail.com
on 13 Sep 2012 at 3:35
Seems reasonable to me. If I have multiple directories listed, and only one of
them is empty, show the same warning? What if I want to ignore that warning?
What if I have tasks that are not file-based - probably doesn't impact anything.
Anyway, as I mentioned earlier, a patch is ideal.
Original comment by konigsb...@gmail.com
on 13 Sep 2012 at 6:17
No problem. Please check if the following functionality would be ok for you:
Workspacemechanic icon changes to warning (like ok sign, but in orange)
whenever one of the directories listed is empty.
The workspacemechanic popup then lists the empty directories. You can select
"ignore" for each of them. When all empty directories are ignored, the icon
changes again to ok sign.
Only impacts file-based tasks.
Original comment by sebidiet...@gmail.com
on 17 Sep 2012 at 10:18
Task repair implies task failure, and you're defining an entirely new state. I
wouldn't bother with the task repair.
Original comment by konigsb...@gmail.com
on 17 Sep 2012 at 11:26
Original issue reported on code.google.com by
sebidiet...@gmail.com
on 12 Sep 2012 at 12:32