Minor Glitch In Dark Radiant Path Browser

[Fidcal]

There's a minor glitch in Dark Radiant you might not know about (or even want to know!) as it would rarely happen. On first run I got 'Engine Path Not Found' so browsed to the drive. There I had both Doom3 and Doom3.OLD folders. The browser was unable to show both; sometimes one, sometimes the other (I think when I switched between name order to refresh), but never both. I renamed Doom3.OLD to xxDoom3.OLD and then it was OK. Not everyone allows for suffixes in folder names - this was also true in DOS it sometimes gave probs. Anyway, if you are using a 3rd party browser you might not be able to fix it but worth being aware of.

[greebo]

Which version have you been using?

 

We switched to the GTK file chooser dialog a few weeks back, so maybe this doesn't apply anymore to the current build.

[Fidcal]

Let's see... v. 0.8.1 - just downloaded this morning.

[greebo]

Ok, that's the latest "release" from January I think. This problem might already be solved in the current development version, so we'll have to check that again when the new release is out.

 

Can we revisit this when this time comes? (shouldn't be very far in the future)

[Fidcal]

BTW, this is not the same file browser as the open/save dialog but a folder browser.

 

Also, while I'm here, dragging all dialogs and child windows around leaves a bad trail lagging behind them. You know what I mean? They clear up in a second but looks like DR is not redrawing fast enough to keep up. Is that a known flaw? Or something odd with my setup? XP Home with 3.06Ghz celeron but old gforce FX5900. Should be enough. I've not had time to do much yet but install it. Before I was using the ordinary editor.

[greebo]

The engine path browser may have been affected by the recent updates as well, but I have to check that. Thanks however for pointing that out, I'll look into it.

 

edit: I think that file chooser dialog has been replaced recently.

 

Concerning the window trail/lag stuff: I know what you mean. I think this is because of the GTK idle draw, but I may be incorrect. (It never bugged me much as I don't drag the windows around very often, however.)