Hi all!
to try and flush out some issues, I reinstalled mac os. Shock horror, issues remain. Turns out I'm not holding it wrong after all..
Anyway, I use ulysses for composition and noticed that when I create a new sheet when in a group, it appears at the top of the list rather than placing it in line, IE, I select a sheet, hit command N and a new sheet should appear below the one I've selected.
I've checked the sort is on manual. I've tried resetting voiceover to factory settings to see if that was an issue, no luck.
I'm not sure if it is a bug in the latest release of ulysses--it would have downloaded the current version when I reinstalled the os.
In a project of over a hundred sheets, it's getting a little annoying having to cut and paste new sheets into place.
Any help will be be greatly appreciated.
Edit:
Ulysses came back to me with the reason.. It's not a bug, as I stubbornly maintained, but expected behaviour. I've pasted the response below for any who encounter it:
This is a newly introduced behavior. If you add a sheet and move it to the top/bottom/somewhere in the middle directly afterwards, new sheets will also be added at the top/bottom/middle respectively and automatically. You can βoverwriteβ this behavior by dragging a newly created sheet to any of the three places.
In your case, you would need to move one sheet somewhere in the middle after creating it. Afterwards, all newly created sheets will be placed directly below the currently selected one.
Does this help?
Comments
No Problem Here
I donβt see the issue you mentioned. The version Iβm running is 38.2 on an M1 Mac Mini running macOS 15.5.
No, but...
Mine inserts wherever I am in the list, but could it be that you're not interacting with the list? Sorry, didn't try it just now when I was at that computer. I had to set a Ulysses activity set to "Ignore Groups" in order for focus changes to work correctly. E.g., I would hit enter on a sheet and discover when I tried to jump to next heading that focus was still on the sheet list. They reproduced it, but didn't do anything about it in the last update.
Contact the support
You should contact the support. Most times theyβre really helpful and if it is a bug, the give it to the developers.