Page 3 of 3

Re: history problem

Posted: 17 Sep 2009 21:27
by admin
tedy wrote:Telling the truth I don't understand what exactly you do mean by the last post.
My screenshot shows the history state showing the "current" position flag next to an invalid path. All we wanted is the right pane (Details in this case) to be replaced by the same thing when I click on an empty DVD drive in this exact case. I see D:\Temp but the history state indicate I'm on the invalid D:\Temp\other.
The question is: what do I do with the Tree? All must be in synch...

Re: history problem

Posted: 17 Sep 2009 21:34
by tedy
admin wrote:
tedy wrote:Telling the truth I don't understand what exactly you do mean by the last post.
My screenshot shows the history state showing the "current" position flag next to an invalid path. All we wanted is the right pane (Details in this case) to be replaced by the same thing when I click on an empty DVD drive in this exact case. I see D:\Temp but the history state indicate I'm on the invalid D:\Temp\other.
The question is: what do I do with the Tree? All must be in synch...
What do you do when I click on my empty F: DVD drive? :)

P.S. Maybe a simple solution would be after a rename, to update history entries that match the "old" name, to the new one..

Re: history problem

Posted: 17 Sep 2009 21:51
by admin
tedy wrote:
admin wrote:
tedy wrote:Telling the truth I don't understand what exactly you do mean by the last post.
My screenshot shows the history state showing the "current" position flag next to an invalid path. All we wanted is the right pane (Details in this case) to be replaced by the same thing when I click on an empty DVD drive in this exact case. I see D:\Temp but the history state indicate I'm on the invalid D:\Temp\other.
The question is: what do I do with the Tree? All must be in synch...
What do you do when I click on my empty F: DVD drive? :)

P.S. Maybe a simple solution would be after a rename, to update history entries that match the "old" name, to the new one..
Indeed, not a bad idea... :)

PS: but does not solve the problem if another process does the rename.

Re: history problem

Posted: 17 Sep 2009 23:01
by tedy
Let other processes worry about :) .
If I use XY, I do not use Explorer, and I can't remember of much other programs renaming directories (maybe some IDEs, editors etc. having built-in explorers..).
Anyway, whatever solution you think is best. Even a simple tip on the screen that the chosen entry is invalid, a flash or anything. Maybe an animation of explosion :) . Just kidding.

Re: history problem

Posted: 18 Sep 2009 15:40
by tedy
Don, I feel a bit awkward but..again.. :)
Firstly I want to note that this is not rare occasion with invalid paths. I often delete directories that I visited before, and this causes the same behavior - invalid paths in history that get into my browsing again and again during the life of the tab - definitely unacceptable with current blocking dialog boxes that popup in 0105 beta.
2 things:

1. The dialogs are blocking - I have to click OK every time I go through this nonexisting entry. I know Explorer behavior is the same but... not usable to having to kill the tab and reopen it again to get rid of these blocking popups.
2. When I use my mouse to go back and forth (4 and 5 mouse buttons, which is 100% of the cases) there are 2 (two) identical popups when XY encounters invalid path. One when I press the button, and the other when I release it. I use standard Windows drivers for the mouse, never used any third party with this installation.

Thanks.
By the way, I see you implemented the rename folder reaction and it now changes the history too, this is perfect. But deleting directories is another matter.

Re: history problem

Posted: 18 Sep 2009 16:16
by admin
tedy wrote:Don, I feel a bit awkward but..again.. :)
Firstly I want to note that this is not rare occasion with invalid paths. I often delete directories that I visited before, and this causes the same behavior - invalid paths in history that get into my browsing again and again during the life of the tab - definitely unacceptable with current blocking dialog boxes that popup in 0105 beta.
2 things:

1. The dialogs are blocking - I have to click OK every time I go through this nonexisting entry. I know Explorer behavior is the same but... not usable to having to kill the tab and reopen it again to get rid of these blocking popups.
2. When I use my mouse to go back and forth (4 and 5 mouse buttons, which is 100% of the cases) there are 2 (two) identical popups when XY encounters invalid path. One when I press the button, and the other when I release it. I use standard Windows drivers for the mouse, never used any third party with this installation.

Thanks.
By the way, I see you implemented the rename folder reaction and it now changes the history too, this is perfect. But deleting directories is another matter.
:) no problem!

1. ok, agreed. Statusbar message will do as well.
2. strange. does that mean that you always jump 2 stations when you move through history by these buttons?

Re: history problem

Posted: 18 Sep 2009 16:39
by tedy
admin wrote: :) no problem!

1. ok, agreed. Statusbar message will do as well.
2. strange. does that mean that you always jump 2 stations when you move through history by these buttons?
Yes, maybe a statusbar message in red, in some section. But I still cannot think of what is the best location we go after invalid path is encountered.
As the screenshot below shows, the current selected entry is on the invalid path, which is confusing because I see D:\Temp in the list and in the tree.. Maybe just skip it like before, and a red statubar message will indicate we skipped a invalid path and it stays until I do any action in XY. Much like other such messages I saw in the interface.

No, the 4 & 5th mouse buttons work normally. Just when I step on the invalid path I get one dialog when I press, and another when I release the 4 or 5th button accordingly.

Screenshot

Re: history problem

Posted: 25 Sep 2009 22:38
by tedy
:) Thanks, Don!
In 0111 I see invalid history entries cause a red notice in the statusbar.
I hope I'm not becoming insolent but...
Wouldn't it be better if that red notice disappears when we step onto a valid path (entry) ? As it is now, if I go even further back in history, the message stays as if all paths are invalid until I select a file or something else. So it is still confusing. I guess this will be a fast fix. I know we talked about that but now I think it should disappear when the current path is valid.
Thanks.

Re: history problem

Posted: 26 Sep 2009 10:51
by admin
tedy wrote::) Thanks, Don!
In 0111 I see invalid history entries cause a red notice in the statusbar.
I hope I'm not becoming insolent but...
Wouldn't it be better if that red notice disappears when we step onto a valid path (entry) ? As it is now, if I go even further back in history, the message stays as if all paths are invalid until I select a file or something else. So it is still confusing. I guess this will be a fast fix. I know we talked about that but now I think it should disappear when the current path is valid.
Thanks.
Oh yes, sure. :)

Actually, I think this type of message needs a different handling altogether. I plan to add something like a quick fly-out message (or whatever it's called) as you see in it Firefox sometimes -- a kind of small unintrusive self-destroying message box.

Re: history problem

Posted: 26 Sep 2009 13:45
by tedy
Fully agreed :)
I thought of the same before but I guessed it would have been too hard/slow to implement.

An unobtrusive self destructing box or something would be perfect.

Re: history problem

Posted: 27 Oct 2009 10:14
by Gandolf
Another history problem:

Executing the Run command "K:\xy TEST\XYplorer.exe" J:\ on a cold copy of XY starts XY viewing Drive J:\ as expected.
Select a path "2009" then "May" then "15" and all is fine.
Now go back: "J:\2009\May\"; "J:\2009\"; "Desktop\"!!!! Where did "Desktop" come from? It's not been visited at all.
It appears that the path passed to XY in the command line does not get recorded in the history so it is not possible to go back to the path passed in the command line. From a cold start, I know I can go Forward from Desktop then Up to the parent because there is nothing before Desktop. However, it doesn't work if there are other previously visited paths in the history because which is the start point?