Hi there,
tl;dr see the discussion I created here
https://github.com/microsoft/vscode-cpptools/discussions/8523. However,
I wanted to discuss that topic here aswell, because it may not be a
generic problem of the plugin, but maybe be dependent only on the LO
project. Additionally, users buovj
On 11/12/2021 15.40, Christian Ohrfandl wrote:
I have the problem that vscode-cpptools "dim inactive regions" option
dims the region in the statement
`#if GTK_CHECK_VERSION(4,0,0)`
and additionally Intellisense also does not work in that region.
When changing the statement to
`#if GTK_CHECK_V
Hi *,
On Sat, Dec 11, 2021 at 3:41 PM Christian Ohrfandl
wrote:
>
> Hi
> tl;dr see the discussion I created here
> https://github.com/microsoft/vscode-cpptools/discussions/8523.
disclaimer: didn't read that yet :-)
> […]
> So where does the vscode-cpptools know the GTK version from and
> theref
Hello together,
thank you for pointing out your ideas!
I am currently working on ibreoffice/vcl/unx/gtk3/gtkframe.cxx.
As for the 'vscode/c_cpp_properties.json' file: If I delete the gtk-3.0
line entirely and restart VS Code, nothing changes; so I guess that - as
Christian pointed out - the i
Hello Michael,
thank you for your quick reply. As you can see from the answer of my
other mail, you exactly hit the spot with mentioning adding
'--disable-gtk3' to 'autogen.input'.
Thank you really much for supporting me!
Kind regards,
Christian
On 13.12.21 07:38, Michael Weghorn wrote:
