From the old Wordpress board..
Mark Gillespie says:
March 9th, 2007 at 4:12 am
Still exhibiting the bug in build 425, opening files when using the tabbed Interface from a source control problem with Cirrus already running.
Not sure if you had planned to address this in 425, but if you have, it’s still borked
Scooter says:
March 9th, 2007 at 9:54 am
Mark, the solution is to add the new /solo switch to the command line called from CM. Have you tried that?
Thanks,
Tim
Mark Gillespie says:
March 14th, 2007 at 7:38 am
I have tried the Solo switch, and it opens new sessions of Cirrus in new windows, not new tabs.. Kinda defeats the point of having tabs…
Michael Bulgrien says:
March 14th, 2007 at 9:44 am
The whole point is that sessions launched by source control should be isolated instances to preserve their integrity. I don’t know of any other merge product that opens source control sessions in a child window under an already open merge product. The tabbed interface is to support all other user initiated sessions.
Scooter says:
March 14th, 2007 at 10:07 am
Michael is correct, the whole point of /solo is to open a completely independent instance of Cirrus. It was the easiest way for us to deal with CM wanting to know when Cirrus is done with the temp files so CM can delete them.
We have sketched out a more sophisticated design where a new instance of Cirrus runs hidden, passes the filenames onto an existing instance of Cirrus, waits for a message saying that comparison has been closed, and then exits.
So, it’s possible we could support the behavior that Mark expected. However, I expect that some people would prefer to have independent windows for the diffs and merges spawned from their content management system.
Tim
Mark Gillespie says:
March 9th, 2007 at 4:12 am
Still exhibiting the bug in build 425, opening files when using the tabbed Interface from a source control problem with Cirrus already running.
Not sure if you had planned to address this in 425, but if you have, it’s still borked
Scooter says:
March 9th, 2007 at 9:54 am
Mark, the solution is to add the new /solo switch to the command line called from CM. Have you tried that?
Thanks,
Tim
Mark Gillespie says:
March 14th, 2007 at 7:38 am
I have tried the Solo switch, and it opens new sessions of Cirrus in new windows, not new tabs.. Kinda defeats the point of having tabs…
Michael Bulgrien says:
March 14th, 2007 at 9:44 am
The whole point is that sessions launched by source control should be isolated instances to preserve their integrity. I don’t know of any other merge product that opens source control sessions in a child window under an already open merge product. The tabbed interface is to support all other user initiated sessions.
Scooter says:
March 14th, 2007 at 10:07 am
Michael is correct, the whole point of /solo is to open a completely independent instance of Cirrus. It was the easiest way for us to deal with CM wanting to know when Cirrus is done with the temp files so CM can delete them.
We have sketched out a more sophisticated design where a new instance of Cirrus runs hidden, passes the filenames onto an existing instance of Cirrus, waits for a message saying that comparison has been closed, and then exits.
So, it’s possible we could support the behavior that Mark expected. However, I expect that some people would prefer to have independent windows for the diffs and merges spawned from their content management system.
Tim
Comment