Seeing some success. Logic is to have the extension hide Bike’s default ordered list decoration and display decimal list instead. Still have some layout fixing to do.
Goal is to make those numbers eventually readable for Go To... commands.
2 Likes
Neat! Though think getting those into Go To is going to be difficult, impossible. Even if I change Go To to run the style system, it would be really expensive. The style system is fast because it only runs for visible rows.
Regarding the layout. I wonder if there are outside the box approaches that you could take, that don’t require making space by indenting the row text. Maybe put the number’s out to the right edge? Or to the leading side of the expand/collapse handle?
I don’t know. For me it’s a hard problem. I think the thing to remember (at least for me) is Bike is an authoring surface. Doesn’t need to look like a final document, just want to cleanly communicate the same information. Use a separate “publish” top to create the final document.
2 Likes
Ah! I had a feeling there might be an issue there but haven’t really investigated. Thanks for confirming.
My use case for this is purely “internal”. I remember and refer to chapters and scenes by numbers rather than titles (chapter 23, scene 34.1 etc), and when those get shuffled around, I want the numbers to follow. I guess there are other ways with scripts and AI to keep numbers consistent, but this seems like a cleaner solution if I can get it to work in a way that isn’t too messy.
For this case I think a script/extension might be the most satisfactory solution. You could just have a “renumber” command that scanned through all your # rows (headings for example) and updating the numbering. Then Go To would work.
1 Like