siliconman01 wrote
It looks like there is something globally wrong with the maximize button on windows resizing. It takes two clicks to get a window to maximize.

Can anyone else reproduce this?

siliconman01 wrote
Windows 7 x64 Professional.


I would like to see the Registry Compactor permit compaction of these small sized hives even though the percentage check shows it to be too large.

I have now made some changes. The logic behind this feature is now the following:

If the original size of the registry hive is smaller than 400 KB, the compact is aborted if the compression is over 90%.

If the original size of the registry hive is larger, the compact is aborted if the compression is over 50%.


Before, the compact was aborted if the compression was over 40% for any sized hives.


I hope this will do it.

Leonardo wrote
siliconman01 wroteIt looks like there is something globally wrong with the maximize button on windows resizing.........

In my case, build 974 with W7 x86 Professional, the jv16PT main window 'maximize button' does not work at all!

This is by design and this was not changed for build 974.


The maximize button for the main window is disabled because some major software download sites use that as one review criteria: if the main window of a program contains a maximize window button, yet the window doesn't contain much content, they will classify the maximize button as unnecessary and reduce the points for the software.

Leonardo wrote
W7 x86 Professional with Build 974:

Clean & Fix my Computer, using search word = zonealarm, CFMC status bar shows Selected: 0, highlighted: 0, total:-2

This is now fixed, thank you for reporting!

jv16 wrote
siliconman01 wroteIt looks like there is something globally wrong with the maximize button on windows resizing. It takes two clicks to get a window to maximize.

Can anyone else reproduce this?

No. With a Windows 7 Home Premium desktop, it only took one click. Did that with the History Cleaner, File Cleaner, and Registry Cleaner results windows.

tullik wrote
The knotty problem of extracting, for the GUI display, the full file or directory reference from some registry values still exists.


However, as long as the "does not exist" decision is based on the correct value and not on the incorrect reference shown in the GUI, it is just cosmetic, although it is moderately confusing.

I agree, it is more or less confusing. But I'm afraid there is very little I can do about the problem. The problem boils down to the fact that it's impossible for a computer program to guess which part of a string is a filename or directory.


This is why most registry cleaner products produce so much false positives and cause problems. PowerTools doesn't produce false positives because its engine checks the strings using all the possible permutations.

jv16 wrote
siliconman01 wroteIt looks like there is something globally wrong with the maximize button on windows resizing. It takes two clicks to get a window to maximize.

Can anyone else reproduce this?

yes, I do (XP SP3)

A very minor issue:


In the History Cleaner (for example), when a group is selected, the group line is counted in the status bar as highlighted whether it is or not.

Capture highlighted.JPGCapture not highlighted.JPG

jv16 wrote
tullik wroteThe knotty problem of extracting, for the GUI display, the full file or directory reference from some registry values still exists.


However, as long as the "does not exist" decision is based on the correct value and not on the incorrect reference shown in the GUI, it is just cosmetic, although it is moderately confusing.

I agree, it is more or less confusing. But I'm afraid there is very little I can do about the problem. The problem boils down to the fact that it's impossible for a computer program to guess which part of a string is a filename or directory.


This is why most registry cleaner products produce so much false positives and cause problems. PowerTools doesn't produce false positives because its engine checks the strings using all the possible permutations.

Difficult, but not impossible. For example, the operating system can (usually) tell.


The values in the three examples I posted earlier all terminate with a backslash. I think that means they have to be directories.

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

tullik wrote
A very minor issue:


In the History Cleaner (for example), when a group is selected, the group line is counted in the status bar as highlighted whether it is or not. ...

This happens only when the entire group is selected. That is, all lines in the group have a check mark.


If you uncheck one or more of the lines, the highlighted count magically becomes correct for the group line whether it is highlighted or not.

tullik wrote

This happens only when the entire group is selected. That is, all lines in the group have a check mark.


If you uncheck one or more of the lines, the highlighted count magically becomes correct for the group line whether it is highlighted or not.

I think this issue got fixed with the other counting problem that I reported fixed earlier in this thread.


In any case, I'll release a new build here for final checks. The same build will be later released officially.

Build 975 released:

http://www.macecraft.com/downloads/betas/jv16PT2010_b975.exe


It contains the fixes reported in this thread earlier by me. If no major issues are found from this build, it will be officially released, most likely later today.

Windows 7 x64 Professional, Clean install of B975


The following issues are still not fixed.


http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4239#p25946


http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4239#p25949

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

I don't know if you intended to fix the missed registry keys as reported in the link below. If so, then it is not fixed.


http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4239&start=0#p25951

Running XP-Pro-SP3 with build 975:


Registry Cleaner -> Scan result list -> Resizing the column width by clicking in the header on the column separator vertical lines repeatedly causes a messed up the display screen (headers disappear and/or do not match colums, column width seems frozen .....). I tried it 3 times repeatedly. Could not even make a screenshot with Irfanview. On closing Registry Cleaner an application error occured, see attached Bugreport.zip!

Leonardo wrote
Running XP-Pro-SP3 with build 975:


Registry Cleaner -> Scan result list -> Resizing the column width by clicking in the header on the column separator vertical lines repeatedly causes a messed up the display screen (headers disappear and/or do not match colums, column width seems frozen .....). I tried it 3 times repeatedly. Could not even make a screenshot with Irfanview.

Do you mean you double click the line between two columns?

jv16 wrote
Leonardo wroteRunning XP-Pro-SP3 with build 975:


Registry Cleaner -> Scan result list -> Resizing the column width by double clicking in the header on the column separator vertical lines repeatedly causes a messed up the display screen (headers disappear and/or do not match colums, column width seems frozen .....). I tried it 3 times repeatedly. Could not even make a screenshot with Irfanview.

Do you mean you double click the line between two columns?

YES, and I attached a Bugreport on my previous post!