sourcer42

Being relatively new to both wxPython & Python in general, I am open to spend some time trying update to Python 3, though I am not at all sure what is involved and I might be in over my head from the get-go :-) FWIW, I would prefer to work under Windows and VisualStudio Code, though I do have a Mint VM box available. Already tried to run TC in a Python 3 environment and got pretty well nowhere real fast. :-)

My current test show that IMDisplay has several memory leaks due to allocation at memory.c line 242

After several days of fiddling with the various options, I think I have been able to get the MSVC 2015 single library 64-bit version to compile and link. For these test, I simply 'cloned the VisualMagick directory to a new version VisualMagickTest alongside the old directory. Currently, I am only building the 64-bit version. Unfortunately, configure is part of this tree and I have not tried to come up with a version which is 'outside' the VisualMagick tree. That would seem to involve changing the...

FWIW, it seems I have been able to fiddle the file All.vcproj.in I am attaching a zipped up version and if you get a chance to test it for the 64 bit version, let me know how you make out. Fortunately with my PC & a good SSD drive, conversion to MSVC 2019 takes 'only' about 7 mins. Compiling the works seems to take one quarter of that time :-) Also, some of the compiler warnings - the warning MSB4211 - can be avoided if one exits the IDE and restarts it. The rest are still there, but this cleans...

In the past I have used MSYS and its relatives , but being steeped in MSVC, I find them more of something I can (reluctantly) use if I have to. Same goes for CMake based projects and they too fall into the same category, I'm afraid. Just how feature complete the vcpkg package(s) is/are, I have not sorted out yet, since I had only installed the basic version. It is very likely, I might investigate it a bit more. For me, the important thing is that it supports what I need. From your POV, that isn't...

FWIW, when loading the VisualDynamicMT.sln in MSVC 2019 ends up with the project All unloaded. Attempting to reload the project produces an error message to the effect that that project does not contain any 64-bit project, or word to that effect. Opening the file %base%\VisualMagick\All\All,vcxproj in a text editorand replacing all 'Win32' strings with 'x64', saving the file will allow the All project to be reloaded. Whether that problem stems from some issue in the original file or whether it comes...

Back at it a bit more. From other projects I am used to the various versions of MSVC having issues with loading and updating older projects. On the whole, things have gotten a bit better, with fewer hiccups from older project with MSVC 2019. Unfortunately, M$ have changed much in their default expectations and hence all the warnings. I have not yet tracked down the issue with the 64-bit All project and am not sure it is worth the trouble. Before I started build the latest version myself again, I...

OK, restarted the 64-bit with fresh download of the repo to a separate directory, then run configure to build a 64-bit DLL version. After conversion of the old sln file, MSVC 2019 (up-to-date) complains: "Current solution contains incorrect configuration mappings. It may cause projects to not work correctly. Open the Configuration manager to fix them" Opening the Configuration manager shows the All project locked to Win 32 for all solution and platform configuration and none of the usual ways to...