Hi, i don´t know the right name, but there are those small icons for "back/forward/up/open in other side/swap/toggle/close", & since the new version
using the "open in other lister" function will crash!
gaah, this is a not so nice one, please fix asap! I use this function a lot. thx.
Well, it here occurs perhaps in 50% of all tries, but i couldn´t make out a certain culprit pattern, though. Seems to be random, one time happening while trying from left to right, then vice versa.
I appended a few minidumps per pm, it that´s ok. I also tried using an older backup (.ocb), with the same results, reinstalling 220.127.116.11 didn´t help either.
What i tried, but without any effort, to build a work-around button a lá "GO newtab OPENINDUAL", that would open the current lister in the opposite window. Please give me some hint, how this possible.
& yes, this time i´ve read the manual, but still can´t figure out the right steps.
If you run that do you get the crash? If so then maybe the problem is due to simply reading the directory in more than once. The FAQ on crashes when reading directories may help if that's the case. (If the command doesn't cause the crash, and only the file-display-border button does, then the FAQ probably isn't relevant.)
If you run that do you get the crash? If so then maybe the problem is due to simply reading the directory in more than once. The FAQ on crashes when reading directories may help if that's the case. (If the command doesn't cause the crash, and only the file-display-border button does, then the FAQ probably isn't relevant.)[/quote]
Hi, & thx, Nudel.
The button works perfectly, no crashes whatsoever. So this is a very nice work around. I didn´t have major, if any, changes in Windows/program environment, because this would be a possible "third party" source for errors.
I am using System Safety Monitor (a HIPS, Host Intrusion Preventing System), which never caused any problems regarding Dopus or any other application.
Still i supected it a bit to possibly cause that problem, since it treats Dopusrt.exe as an extra application (But as i said, i never had any problems with it since april 2007, when i started using Dopus, vrs 8 back then, but who knows?).
I only say this in case of nobody could verify this particular bug on another machine, which would mean, some very specific interaction on my machine is causing this error.
Or it is something regarding that new button for loading sets of tabs, which i use since a few days? I don´t think that it´s the reason, though.
It is a three way button (i asked in that other thread here recently), which is loading different sets of tabgroups, like
Go TABGROUPLOAD=group1 OPENINLEFT
Go TABGROUPLOAD=group2 OPENINRIGHT
for LMB, & another set loading other groups for RMB.
So basically i have to save each group accordingly to how they´re supposed to open the tabs (there are currently 2-3 tabs in each group).
Hi, i have to apologize, i somehow made a awful mistake, saying that it happens randomly. It does not! I perceived it in a wrong way anyhow, maybe because it happens in both directions, but it only happens with my "normal" layout, more precisely from
K:\Filme to L:\Web\neu
& ONLY THEN it will crash!
This are the two tabgroups
& now i remember, either the "L:\Web\neu" or "L:\Web" folder had, for no apparent reason, power mode view instead of details mode. I´ve changed that & saved it under "folder options", chosing the "for this folder only" option. I guess i have to rearrange all settings & resave them, which hopefully will solve the problem. I will post it then here, ift it worked out ok.
now i deleted "normal" & "normal2", the both tab groups represented in the two screen shots & rebuilt them, it´s still crashing in both directions K: <-> L:, or any other combination with drive M:.
I have a internal PATA disk, which holds drives C - I, & an external USB-SATA-disk, which is drives K, L & M, which is suspicious. Seems to be a somewhat complex issue. (I even had a look in the NTFS security tabs of either drive, but to me it looks quite normal (i could post them anyway, if that helps).
Now i deleted "normal" & "normal2", & created two new tabs with new names, it still crashes.
But the very strangest thing of all: if i load the other tab group ("Go TABGROUPLOAD=group3 OPENINLEFT
Go TABGROUPLOAD=group4 OPENINRIGHT, which is the RMB loading a different initial set of tabs) & then navigate to the corresponding problematic combinations of K:, L:\ or M:\ drives & try it - there are no crashes at all! what the...
Other posts from Abr which ended up in the wrong thread.
Note: We cannot merge threads, only split them, so if a post ends up in the wrong place, re-post it in the right place and let an admin know that the wrong post needs deleting.
[quote="abr"]after removing all "locks" from the tabs, there are no more crashes. I just found out.
On the other hand (showing that the PATA vs SATA approach was wrong) i can reproduce this bug with any drives, let´s say F:\ & H:, only by creating tabs which are locked (tested with the middle lock option, simple lock) & sending them to the opposite lister - > crash.
It is possibly in combination with one of the two new options i´m using most recently, tab_click_nofocus, because i use locked tabs quite a while & didn´t see that crash before.[/quote]
i found the problem. It is not about PATA vs SATA Disks, i can now reproduce that bug with any drives!
It is because of the tabs being locked!
Any locked tabs will crash when trying to send them to the adjacent window. Furthermore i guess, that this only occurs using the tab_click_nofocus feature (which i use since ~ two days, that´s about when i noticed those issues).
I removed all locks & there is no crashing anymore.[/quote]