Drag & Drop broken during copying

[Creat]

I've found another bug: If you copy/move some files around so that the usual "Copying..." or "Moving..." progress-window is open you can't drag & drop files anymore. It won't let you grab anything (Explorer f.ex. still alows you to). This is a real problem for me since I don't usualy open a new explorer (or TrackerV3) instance whenever I copy or move stuff around (which I do alot). Esp. since Tracker has multiple tabs it should allow me to do more than 1 copy/move operation at a time.
It also breaks my way to open MP3s or videos, since I often just drag them onto the player (winamp, mpc, ...).

I know this might not be a high priority, but it's a real important one for me

edit: I just noticed that some shortcuts (f.ex. Ctrl+W to close the tab) also don't work anymore while copying

thx and keep up the great work!
Creat

[admin]

If the documentation is right, the file operation progress window should be modal now (main/parent window disabled). I never really checked that, but what you say seems to confirm it's modal.

Now you want it to be modeless. It can be done, but that shifts some responsability to the user because e.g. file listings of files in the state of being moved might not be updated yet so you can easily create errors if you're malicious enough

On the other hand, if Explorer does it too, let's see what happens! The next BETA will have it modeless and you tell if it works as you expected.

[Creat]

Well you can still use Tracker if a copy is in progress, but some stuff just doesn't work anymore (like the shortcuts), while other stuff still does. You can still navigate - at least in the directory you're in, somtimes in others too, not quite sure when you can and when you can't. So if the current directory is the one being copied and you delete some files the copy also stops when it reaches the now-gone files. Long story short, if you really try to break something you probably will

So this is not really modal either, you can still use the main window (thank god!) at least to some extent.

Well I'm glad you agreed to make it like explorer, since it's really annoying to have to open up many instances all the time just because I copy some stuff around...

Oh I just found another bug (tracker crashes) related to that. Since I'm used to working with only 1 instance I close the tracker that copies things at the moment and open another one. The closing detaches the copy window (well tracker still stays in memory, but the main window closes and the copy window gets it's own taskbar button as soon as it gets the focus, it's the same way exporer does it). Unfortunately as soon as the copy/move is finished the (already closed) tracker-instance crashes with a "Runtime Error 91: Object or variable not set" or something similar.

Just to explain how I got the idea of closing an instance of a program copying stuff in the first place: Explorer has this weird behaviour that if it copies/moves something and you minimize it, you can't restore it until it has completed the file operations. So I usualy right-click on taskbar and close it. Luckily Tracker doesn't do that, you can minimize and restore it also while file operations are underway. It was just a habit I guess

[admin]

Oh I just found another bug (tracker crashes) related to that. Since I'm used to working with only 1 instance I close the tracker that copies things at the moment and open another one. The closing detaches the copy window (well tracker still stays in memory, but the main window closes and the copy window gets it's own taskbar button as soon as it gets the focus, it's the same way exporer does it). Unfortunately as soon as the copy/move is finished the (already closed) tracker-instance crashes with a "Runtime Error 91: Object or variable not set" or something similar.

Oh yes! Well, the natural answer would be not to allow to close the app while "its" file operation is in progress. Any problems with that anybody?

[admin]

Well I'm glad you agreed to make it like explorer, since it's really annoying to have to open up many instances all the time just because I copy some stuff around...

Did you actually try it and do you confirm that it works alright now?

[Creat]

yay my hero

yes, it detaches the copying windows right from the start now.
This is also quite helpful since I don't have to drag them out of the way, like I have to do with explorer, to get to the navigation tree on the left (usualy whatever you need is right under it).

[sorry, it took me so long to reply]

thanx alot!
Creat

[Creat]

Turns out it's not completely fixed...
If I copy from a network location, I can't keep on using tracker. I can't select a different file, though I can change the directory and when I change back I can. Drag&Drop and shortcuts don't work in that case though (neither before nor after changing dir once or twice)

Also, I start tracker from a shortcut in my QuickLaunch (or however that bar next to the start-button is called) and the first "copying..." window that appears is always maximized (even though it's a dialog window that shouldn't be able to do that). I assume it has something to do with the fact that the shortcut has set "Run" to "Maximized". It only happens on the first copying/moving though...

Bye
Creat

[admin]

Turns out it's not completely fixed...
If I copy from a network location, I can't keep on using tracker. I can't select a different file, though I can change the directory and when I change back I can. Drag&Drop and shortcuts don't work in that case though (neither before nor after changing dir once or twice)

Sorry, I have no idea why that should be the case. There are things we know but cannot understand...

Also, I start tracker from a shortcut in my QuickLaunch (or however that bar next to the start-button is called) and the first "copying..." window that appears is always maximized (even though it's a dialog window that shouldn't be able to do that). I assume it has something to do with the fact that the shortcut has set "Run" to "Maximized". It only happens on the first copying/moving though...

Weird, looks like a QuickLaunch bug to me. I have no influence on that behavior from TV3's side.

[Creat]

Ok I've done some more testing since I couldn't sleep tonight

It actually has nothing to do with where I'm copying from (network or local).

bug no. 1:
Whatever part of tracker is used to start the copying gets disabled for mouse inputs until the copy process is finished or the part gets reinitialized. What I mean by that is if I drag-drop a folder from the list view onto some folder in the tree view or in the list view, the list view doesn't work anymore. I cannot click on any files to select them, doubleclick a folder to enter it (open it). I can use the up/down keys to change current files though.
But when I select a different folder in the tree on the left (or use the keyboard to navigante to a folder and press enter) , I assume there is some sort of reinitialization done in the list view (after all it's cleared and filled with the content of the new folder) because then the mouse works again in it.
If I drag a folder from the treeview onto another one (target can again be in the tree or list view, doesn't matter like above), the treeview doesn't respond to mouse input anymore. Since I don't know of any way to reinitialize it mouse input stays disabled in the treeview until the copying is finished (ctrl-f4 doesn't work either, see below).

bug no. 2:
As long as a copy process is running, no keyboard shortcuts are working. This includes F4, F5, Ctrl-F4, Ctrl-C, Ctrl-V and a few more that I tried. I didn't find any that still work, so listing would be pointless

bug no. 3:
Even if I get the mouse working again like described in bug no. 1 above, or if I use the still working of the 2 windows (list/tree), drag & drop is not possible while a copy is underway. I just can't grab anything. Tracker can still be used to drag stuff onto though from another tracker instance or an explorer window BUT doing so leads to a crash as soon as both copys are done (or aborted), it doesn't matter which one of them is canceled/done fist. The error is [The instuction at "0xrandomaddress" referenced memory at "0x00000000". The memory could not be "read".]
I didn't try to start more than 2 copy processes like that since this already seems to have some issues

bug no. 4:
Tracker still exits abnormaly if you exit tracker while a copy process is still running. It's still a runtime error '91'. I think it should be possible to exit though since tracker isn't doing anything (as the copy is done by windows) and the window does close correctly. The error appears as soon as the copy finishes.

It would be really great if you could get this to work, I often initiate more than 1 copying process and I'd hate to start another tracker for it everytime, esp. since I can't close the old one without getting the runtime error. A good example would be to copy files to the harddrive from 2 or more CD/DVD drives. Or from the network and a CD/DVD drive and so on...

I really hope this helps, and I hope you can reproduce the effects I described here

bye and thank you
Creat

[admin]

Hmmm, looks like some deep research has to be done... at the moment I don't see anything I could do about this.
With one exception: error 91 should be gone forever from the next version onwards!

I wonder if detaching the copy progress did bring anything good?

[Creat]

well all the problems were there before too I think, so it did no harm at least

and I do like that I could (at least as soon as it all works) use tracker without the copy windows hovering somewhere infront of me... definitely a plus

bye
Creat

[admin]

Code: Select all

v4.00.0189 - 26.09.05 13:15
    * The file operation progress window is now shown modeless. Which 
      effectively means that you can go on working while files are being 
      moved or copied in the background.

Well, the original claim of the modeless file operation progress window could not really be fulfilled, right. On the other hand, I see certain irritating disadvantages:

Code: Select all

      Note also that a modeless progress window can easily get lost 
      behind larger windows.

So: I decided to make this option a hidden feature from the next version onwards.