JomiTech Forums

The version number problem actually seems to be solved by turning off this option.
So far I no longer have any problems with DPI awareness.

I turned the option "Compile files/projects without saving them" off.
A first test afterwards was positive regarding problem 2).
I will continue to monitor this and will be able to say for sure in a few days whether the problem has completely disappeared.

I've been using TwineCompile for a longer time - it is a great tool!!! Two things that don't work for me. 1) The DPI awareness does not seem to be adopted correctly. Unfortunately I don't have a minimal example. But when I compile a large project at home and have compiled it the day before with a di...

Perfect - problem seems to be fixed
thanks

Hi TwineCompile-Team, first of all, thank you for developing this great tool. Could you take a look at this problem: https://quality.embarcadero.com/browse/RSP-41766 I believe it is a TwineCompile problem - maybe a regression bug? Or is the bug-fix not in the TwineCompile Version in Embarcaderos Get...

Will there be a TwineCompile update for Embacadero RAD Studio GetIt Package Manager that contains this bug fix?

The time for a build is now drastically reduced. It took ~2400 seconds to build this project using the old TC dll. Now there are 325 seconds needed :-) Both tested with "all warnings on" and bcc64. With "all warnings off" it takes ~320 seconds. If I notice any abnormalities with ...

Yes, warnings issued from inside the VTK header files.
I think it would help if you could exclude folders (and all sub-folder) from the warnings - this should work.

Thank you for taking a look at this issue. A solution to this problem would be a great help when working with large projects in the RAD Studio IDE! TwineCompile can then become truly irreplaceable

247532 warnings.
Most of them from libaries like vtk which I use.
So I can not avoid these warnings.
In the RAD Studio IDE it is just possible to say "all warnings" or "no warnings" for the bcc64 compiler.