Bike 2.0 (Preview 269)

I agree, this is a potentially problematic case.

It’s originating from:

The purpose of Bike Markdown is to allow Bike outlines into markdown workflows. In my mind it really only makes sense to use the .md extension for Bike Markdown. Otherwise no other workflow will recognize it without a file rename. For me that means Bike should both read/write .md.

The problem is what to do when Bike is asked to read .md that doesn’t fully conform to Bike Markdown? Current approach is warn, but allow.

Other approaches I think think of:

  • Disallow, but that creates other problem, such as small valid markdown edits to existing Bike Markdown outlines corrupting them so they can’t open.
  • Add more options such as Open as Plain Text. (Edit, ha, well we had same thought anyway!)

I think this might be the cleanest solution. There is def. a place for Bike Markdown in “vanilla” markdown workflows, so the nuclear disallow option would make no sense to me.

Playing with it a bit more, i now think the problem is that the drag and drop is just slow, which is why i felt like i needed to drag way to the left. It was that i needed to keep the drag active until it took. I am dragging and dropping large suboutlines. So sometimes, when i drag, i get the beachball, and even when i don’t, it takes a couple of seconds for the drag to take. (I’m on an M4 mba with 32 GB RAM, so i don’t think it’s the h/w).

Ah, I can reproduce that. I’ll see if I can speedup case of dragging large outlines.

@Doug Please try the latest release, I think it should get rid of the drag and drop delays you were seeing. I’ve also improved the Commands Explorer UI in various ways. It’s still complex, but hopefully will make a bit more sense.

I still have not been able to really reproduce the keybindings delay you mentioned. When I loaded the keybindings that you sent everything still was instant for me. My best bet at the moment is the issue is related to your outline shape/size. The text:move commands are less performant then the commands that you overload with the keybindings. But it doesn’t seem that that would create a full 3sec delay.

Anyway, please try everything again in latest release and let em know what’s good and what’s still a problem.

2 Likes

Please try latest release and see if it now works as you think it should. I certainly think it’s an improvement.

1 Like

Sweet! The detached copy option is super nice, saves some time. One thing I’m not particularly clear on—if I open as detached copy, and then close the Bike window without saving, does it put the file somewhere, or deletes it? I’m not getting a prompt to save the file if I make no edits and just close the window.

Ah, yeah that’s an edge/bug case. Will fix. It’s treating that case as a new untitled document with no edits. And so it is not autosaved.