What happened: The catergory was created, but does not appear in the sidebar. I therefore set it up again, and now have multiple copies of the same catergory (although now of the instances show in the side bar).
Trying to delete other existng categories brings up a confirmation warning, but clicking on either Cancel or Delete Catergory do nothing - Box is stuck on the screen.
I can replicate this on both iMac and MBP
What I expected: Catergory to appear in sidebar
Things that might be helpful to know (Agenda version, OS and model, etc):
I think what probably happened was an internal crash, leaving the app in a semi-working state. After that, things that you saw were due to the original problem. Relaunching usually fixes that type of issue.
I am on v2.11 and am hitting this also. I created the new category using the “+” in the bottom left corner. Category isn’t visible until I restart Agenda.
Can you tell anything that could indicate when this happens or not? Is it always? Irrespective of via the plus button or via the File menu? When any project is selected, etc etc
same here, creating new category doesn’t show up at all. Dragging projects into another category will not remove the old location and also doesn’t show up in the new location. Restart works, but somehow, creating few empty projects (maybe due to the repetitive tries).
This sounds like it is probably caused by some internal crash. Would be great if the next time you see it, you go into the Console app and see if there is any error there from Agenda. Also, if you see it happen, try the drag you mention, and see if that prints any error in Console.
The same situation happened with me just now. Macbook Pro 2017, Agenda v2.1.1 added via + and by File New Category. I have 3 categories all called the same thing not visible in side bar. I’ll close and restart yet this is something within the app. Thanks!
We have found what’s causing this issue and it will be fixed in the next update. A restart of the app is the current solution. Also, be aware that the most likely scenario to run into this is if you hide the sourcelist sidebar, avoiding that also reduces the chance of hitting the issue.