Bugs: 4.0.b2 GUI related

[schitzn]

I notice when a large file is being moved, JKDefrag becomes unresponsive.  The situations where this occurs are as follows:

1. When the window is minimized

2. When View is set to Stastics.

When view is set to diskmap, JKDefrag is responsive to PAINT events and mouseover events.


The View->Statistics screen does not display carriage returns correctly.

When mouseover events occur, the bottom statistics update to the current mouseover entry.  It would be good if this defaulted back to the current action being performed by JKDefrag when mouseover occured outside of the diskmap.

A couple of non bug related questions.  Where can I find out new features compared to JKDefrag 3.16?  I assume Prefetching is now supported, and that MyDefrag is now closed source.

Congratulations Jeroen on the next step of your Defragmenter.  I am confident MyDefrag will become a common household name for a must have program for PC Performance.  Congratulations on your fame to come!

[jslegers]

The View->Statistics screen does not display carriage returns correctly.

Same problem here.

[jeroen]

I notice when a large file is being moved, JKDefrag becomes unresponsive.

Thanks for testing and for the feedback, I appreciate it! I'm not sure why the program is unresponsive in statistics mode, it shouldn't and I will look into it.

The View->Statistics screen does not display carriage returns correctly.

Yes, it's a bug in the second beta.

When mouseover events occur, the bottom statistics update to the current mouseover entry.  It would be good if this defaulted back to the current action being performed by JKDefrag when mouseover occured outside of the diskmap.

Can you explain more? I do not understand what you mean.

Where can I find out new features compared to JKDefrag 3.16?

I'm sorry but I have not written such a list.

I assume Prefetching is now supported, and that MyDefrag is now closed source.

If you mean boot optimization then yes, it is now supported. And yes, MyDefrag is closed source. JkDefrag remains open source.

[brwainer]

When mouseover events occur, the bottom statistics update to the current mouseover entry.  It would be good if this defaulted back to the current action being performed by JKDefrag when mouseover occured outside of the diskmap.

Can you explain more? I do not understand what you mean.

I have noticed the same thing... What he's talking about is that the bottom of the screen it shows the name/path of what's under hte mouse. That's the feature. The problem we have is that if the mouse moves off the window, say it's not maximized or the user has 2 (or more) monitors, then it shows whatever file the user's mouse passed over last on it's way off the window. In this case, it should be blank or show the current file.

[rlarno]

When mouseover events occur, the bottom statistics update to the current mouseover entry.  It would be good if this defaulted back to the current action being performed by JKDefrag when mouseover occured outside of the diskmap.

Can you explain more? I do not understand what you mean.

I have noticed the same thing... What he's talking about is that the bottom of the screen it shows the name/path of what's under hte mouse. That's the feature. The problem we have is that if the mouse moves off the window, say it's not maximized or the user has 2 (or more) monitors, then it shows whatever file the user's mouse passed over last on it's way off the window. In this case, it should be blank or show the current file.

The current file being processed is listed above the diskmap.
The file listed below the diskmap is the one the cursor is over.
I find the current implementation the correct one. One can focus in on a certain file, and using the keyboard, switch to another window, without the filename changing.
E.g. locate a file that cannot be moved, navigate to the file and use unlocker on it to find out what process has it locked.

[jeroen]

it shows whatever file the user's mouse passed over last on it's way off the window. In this case, it should be blank or show the current file.

Ah, I see. Thanks for the explanation. I will put it on the wishlist to blank the info when the mouse is moved to the rim of the diskmap.

[schitzn]

I notice when a large file is being moved, JKDefrag becomes unresponsive.

Thanks for testing and for the feedback, I appreciate it! I'm not sure why the program is unresponsive in statistics mode, it shouldn't and I will look into it.

Just a heads up in case you miss the other half, when the window is minimized, it fails to respond to taskbar clicks to restore the window or a RMB to bring up the popup menu whilst in the taskbar.  It seems the windows messages arent processed when moving large chunks.

[jeroen]

Yes, thanks for the reminder, I have it on my list to look at why statistics mode is unresponsive when moving big files.