This is one way to do it:
Go CURRENT NEWTAB OPENINDUALIf 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).
But in the meantime i can use the new button. 