#785 Flaws in remembered checkout target logic

[Oliver Giesen]

It seems the checkout target will always point _at
least_ at the parent folder of the current selection
even if a previous checkout initiated from that same
folder specified the folder itself as the checkout
target. If the folder in question is also the root of
the browse location, the checkout target will always(?)
default to the drive's root. At least that's what
happens in my experience - even though I remember at
least one test where it actually worked as I expected.
My tests now however always produce the result
described above.

Also, I think we don't have a tracker item for
remembering the module name override and "don't shorten
module paths" options yet...

[Björn Carlsson]

Logged In: YES
user_id=687086

My experience is that the "Local folder to checkout to" is
always the root. My browsing location is for example
"D:\Mac\Drivers". And when I open the checkout dialog the
"Local folder to checkout to" is "D:\"
I change it to "D:\Mac\Drivers" - and checkout...

Open the co dialog again - and the "Local folder to checkout
to" is "D:\" again :o(
I have expirenced this behavior since the checkout dialog
got it's new look 4 or 5 build ago(?) I am now using 1.3.24.1
Are there any kind of "remembered checkout target logic"?
What about a combo with history?

[Alexandre "Zandao" Drummond]

Logged In: YES
user_id=1531396

The path at Checkout Settings dialog is the result of a
function that traverses the diretory tree starting with the
selected directory and goes up until it finds a directory
that does not contain a CVS subdirectory.