Sigil 2.4.0, what is debugging with VS IDE easier?

[byword]

I am building Sigil 2.4.0 to test and review the newly added features.

• Made debugging with the VS IDE easier

However, I don't quite understand the meaning of this. Could anyone explain how debugging with the VS IDE has been made easier?
There don't seem to be any new settings or features added to Sigil.

[DiapDealer]

I made it easier, but not simple. The first step is configuring the build using a cmake Visual Studio generator (rather than the NMake Makefiles generator).

The bottom line is that I made easier for me to debug Sigil on Windows using the IDE.

It's still quite involved and largely undocumented. Maybe I'll get around to documenting it sometime in the new year. But if you don't have an urgent need to do any Sigil debugging using the Visual Studio IDE. I don't really recommend tackling it. I only do it to get stack traces when investigating crashes. Something we were never really able to easily accomplish on Windows before. I haven't heard of any reliably repeatable Sigil crashes on Windows lately.

And no... debugging with the VS IDE does not involve any settings from within Sigil. So while it's definitely not a user feature, as such; neither is it a bug fix.

[byword]

Originally Posted by DiapDealer

I made it easier, but not simple. The first step is configuring the build using a cmake Visual Studio generator (rather than the NMake Makefiles generator).

The bottom line is that I made easier for me to debug Sigil on Windows using the IDE.

It's still quite involved and largely undocumented. Maybe I'll get around to documenting it sometime in the new year. But if you don't have an urgent need to do any Sigil debugging using the Visual Studio IDE. I don't really recommend tackling it. I only do it to get stack traces when investigating crashes. Something we were never really able to easily accomplish on Windows before. I haven't heard of any reliably repeatable Sigil crashes on Windows lately.

And no... debugging with the VS IDE does not involve any settings from within Sigil. So while it's definitely not a user feature, as such; neither is it a bug fix.

Thank you for your response.
It seems I completely misunderstood. I thought it was a feature to help edit EPUB code by integrating Code View with VS Code. A few people around me use VS Code as a supplementary editor, so I assumed that might be the case.

I am currently translating Sigil's menu into Korean and compiling a Korean version of the Sigil User Guide to help Korean users better utilize Sigil. In doing so, I am trying to understand all of Sigil's features. Especially with new features, if I don’t understand their exact functionality, I sometimes make translation errors, which is why I asked the question.

To me, Sigil is the best EPUB editor.
I am always grateful for it.

[DiapDealer]

Yes. Sorry for any confusion. This particular change has only to do with the compiling and debugging of Sigil itself with the Visual Studio IDE. I compile both Qt and Sigil as Release with Debug Info builds. That way I can use the Visual Studio IDE to set breakpoints when running in debug mode. Doing so gives me actual line numbers and function names in the Sigil source code where/when problems arise. Much more revealing than simply printing QDebug() info to the debug log and inspecting crash dumps.