yeah, the preview v2 is still experimental. the broken image issues should be fixed after today's release. the table border issue I will investigate in terms of changes, preview v2 should sync as your making changes. currently this might lag a few seconds from your typing

in terms of changes, preview v2 should sync as your making changes. currently this might lag a few seconds from your typing

It seems to be working that way now after the reload.

The additions in v50 are great by the way. Looking forward to more (on the labels, etc.). 🙂 The zoom issue is still the same, it might be related to some local OS/hardware settings but am reluctant to change as it works well elsewhere, including in 3D modelling and visual programming interfaces...

Glad you like them! I've got the panning issue scheduled for this week, so I'll let you know where you can tweak the panning settings once that goes live

More of an FYI - there’s a few more Markdown Kanban options in the VSCode Store. None of them are as good as the obsidian plug-in (and none of them play well with dendron) but at least it’s not a total non-starter now

Hey sorry been on vacation and have some more vacations coming up 🙂 However lookups have been working good for me every since

👍

you never need to apologize for taking time off. enjoy 🙂

@User I am finding the graph very useful already. One further idea. What about a toggle in the Lookup that would force/disable synchronization with the open graph? This would allow the use of the search functionality in the Lookup with simultaneous graph visualization that will aid discovery. This can be in addition to the filtering in the graph, unless those ways of searching can be merged somehow...

Might it be useful to have auto-fill in the Refactor Hierarchy command?

Interesting idea - I think that would be both achievable and useful for discovery like you said. I’ll make a note of it

No CROP next week. Lots of features coming out and in progress so please check back next week for new CROPs 👨‍🌾👩‍🌾

When one note is referenced within another and has footnotes, the incoming footnotes appear outside of the text box at the bottom. This seems incorrect and if the host note has references, they override the incoming references causing havoc. Needs fixing, I think.

@User Any word on this one?

I made an issue for this. I think it is not as intended but correct me if I am confused. https://github.com/dendronhq/dendron/issues/1001

When trying to move a note, the first option where a note doesn't already exist fails with "note already exists". I have to select the create new option to move the note. Consider making this the default option or altering the verbiage to make the correct option more obvious.

yes, this would make for a great CROP. can you create an issue for it?

yep, this is a bug. we'll go over it during planning

Exciting to see v51. Any chance items in 'Highlights' could be linked to the places in the Wiki where the relevant features are explained?

Looking at tags... Is this intentional?

good catch. nope, just fixed 🙂

e.g., where can I find the instructions on the Graph styling? I must be blind but....

Oh whoops, I suppose it's hidden at the bottom of the graph view page. You can find it here https://wiki.dendron.so/notes/587e6d62-3c5b-49b0-aedc-02f62f0448e6.html#custom-styling

Feel free to ping with any questions, there are more supported selectors and properties than listed directly on the docs. Those are just the most common ones 😄 You can also just run

> Dendron: Configure Graph Style (css)

, which will make the style file and have a couple of the most common selectors pre-added so you can play around with them

@User Thanks...

Wiki links with unicode characters are not rendered anymore. I use "：" (U+FF1A : FULLWIDTH COLON) instead of a regular colon since you can't put that in a file name.

Thanks for the feedback, I believe I have a fix for this already: https://github.com/dendronhq/dendron/pull/1004 We'll ship the fix with the next version.

Also noticed that auto-suggest for new # tags doesn't seem to work all the time and after you restart vscode, it stops working altogether.

We actually don't have autocomplete for hashtags yet, but that will get shipped next week.

Ah, so when it seemed to work, it must have been a fluke. Thanks!