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...
As I have already wiped out the 64-bit code, I would have to rely on my memory at this point and rather than go down the wrong path, I will raise that issue again when I start to work on the 64-bit code again. IIRC, the issue was related to my trying to build a 32-bit version from the same sln file Now that you have confirmed that the accepted way it to build with 2 code bases, I go with that for now.
It does take a lot of time to upgrade from the original VS 7 solution files - what would it take to eliminate or improve on that? :-) In the process maybe one could also eliminate some of the warnings. From the past experience with the 32-bit version of the previous release, I know I can ignore the warnings - though they do kind of bother me when things don't work as expected. Are there any recommendations for building 32 & 64-bit libs in parallel? I have run into a curious issue with the 64-bit...
Just downloaded the latest 1.3.6 code and started to compile for 64-bit libraries. Using MSVC 2019 I get several warnings regarding jbig85.c(904,31): warning C4267: '-=': conversion from 'size_t' to 'unsigned long', possible loss of data others show in gzread.c & gzwrite.c also libtiff\tif_webp.c(169,55): warning C4244: '+=': conversion from 'tmsize_t' to 'int', possible loss of data
Hello Fulvio, I have known about vvvP for some time and have now gotten back to try and use it more. Initially, using the older version 1.1 I had some issues in running it and eventaully put it aside. After finding the newer version 1.2, I wanted to give it another try, largely because I think it would help me catalog the many images I have on my network. After some trials, I have managed to both run the compiled Windows version as well as actually compile my own copy under Win 10 & MSVC 2017. In...
It bothers me for two (at least) reasons one - because the 'stop' button does not change 'state' - enabled/disabled, I was initially uncertain on whether or not my request for some action was even being received. It does seem to take some time for other signs of 'life' to become apparent. And when one is trying out new, unknown software, one tends to be more careful at the start and look for expected results. two - symmetry: the other toolbar icons are disabled once an action is initiated, though...
Running the non-portable version 7.0.2 under Win 10 64-bit. When I first found Ultradefrag, I noticed this and for a time I rarely used UD. After getting frustrated with my current defragger, I decide to start using UD and I find it very useful, but the fact that both the tool bar button and the action menu item for 'stop' are always enabled bothers me. I have looked at fixing the issue myself, but am not ready to try and port the build process to MSVC just for this :-)
Running the non-portable version 7.0.2 under Win 10 64-bit During both the analysis and optimization phase of a hard disk, the text UltraDefrag 7.0.2 overwrites the feedback in the title bar to the point where it is not only invisible but also annoying because displaying it seems point less if it can't be read ;-)
Even though I would expect very little improvement from a SSD, as a test I tried it anyways. Turns out it is much, much slower for a SDD a quarter of the size of a regular hard disk. Any reason for this?
Disk spanning -> stand-alone archives??
Under Win 7, 1.1 pops up a dialog telling me: Unexpected error .... bad allocation"...
After some more playing with the program, I have finally been able to run 1.1 on...
After some more playing with the program, I have finally been able to run 1.1 on...
After some more playing with the program, I have finally been able to run 1.1 on...
Just downloaded the Windows version of vvvP 1.1 and I cannot get it to work properly...
Just found vvvP and it looks like it might be exactly what I need. Which graphics...
Hi Sebastian, It is good to hear you still monitor the project :-) The source I used...
Hello Sebastian Just found this useful program - from what I have seen so far. I...
the natsort() problem was solved in my case by by the following change in functions.inc.php...