Troubles with autocompletion with VSC and third party packages

unfortunately the nimsaem plugin has some problems. This issue is already known for [autocompletion](https://github.com/saem/vscode-nim/issues/84). In my case, I found that the plugin's autocompletion problem is due to the fact that it only works when you are working in a VSC project "Folder". I

Fidgetty Widget System: Rewrite

Oh thanks! I forgot to bump the required version in Fidgetty. I need to figure out a better setup.

internal error: cannot map the empty seq type to a C type

What about a real bug report with a reduced example that reproduces the problem?

Troubles with autocompletion with VSC and third party packages

Using VSC and telebot I cannot see the auto-completion for the types. It does not give me errors, but when I type code I have to go through the src provided by github because I'm unable to get any hint. I'm using nim 16.6 and I've both installed telebot (otherwise it would give me an error) and

Nim 1.6.8 released!

It needed 2 followups, and it removes some 1.0 support, so it poses a backwards compatibility issue. Maybe one could make another followup that adds back the 1.0 support.

Fidgetty Widget System: Rewrite

You're really unlucky, yet another package version mismatch issue `/tmp/fidgetty/src/fidgetty/themes.nim(28, 38) Error: attempting to call undeclared routine: 'init'`

See generated code after template processing?

Do import macros and use `expandMacros: myTemplate()` Seems to work...

See generated code after template processing?

> Perhaps, I'm missing something here and the templates don't actually generate > Nim code, but C directly - the truth is I haven't looked this one up... They generate Nim code and you don't have to look this up, it's basic knowledge about templates. Your beloved LaTeX works the same way, macro

Nim 1.6.8 released!

OpenSSL 3 support is not mentioned in the changelog. How comes? (see )

See generated code after template processing?

I may have forgotten that it doesn't work with templates, or it may have stopped working. It does work with macros though :P

See generated code after template processing?

Thanks a lot! For some weird reason, I have never managed to use `--expandMacro` \- basically, I don't know what it's supposed to do, or - more precisely - where the expansion is to be shown... As I cannot simply spot it anywhere... :S

See generated code after template processing?

You can use `--expandMacro:templateName` or use the following: import std/macros macro dumpTyped*(ast: typed): untyped = result = ast echo ast.repr Run

See generated code after template processing?

So, since - for better or for worse - I'm making some heavy use of templates and trying to reduce them & debug a few things here and there, I'm wondering how I could have a look into the final/generated Nim code after the templates have been processed. (Perhaps, I'm missing something here and t

Fidgetty Widget System: Rewrite

## Automatic DPI Scale Adjustment I just pushed a change to automatically set the UI scale based on the window's DPI scale. It works on my Mac and Linux machines, but monitor DPI information is fickle. It'd be great to know if it works on low-dpi screens and on Windows machines. ## Layout Widg