Skip to main content
A
Anonymous
May 2, 2011
Answered

New topics added by one user not visible for another user (RH9 & SC)

  • May 2, 2011
  • 1 reply
  • 985 views

Hi everyone,

My colleague and I are trying out RoboSource Control, in order to work at the same project together at the same time. Up until now the test led to the following question:

When user1 adds a new topic to the project (in project manager) it is automatically checked out to him. Then when user1 checks in this new topic it does not become visible for user2. Is there some sort of setting that should be adjusted in order to be able to see the new topics after checking them in?

Thanks for your help!

Roza

This topic has been closed for replies.
Correct answer

According to all the posts I have seen, the XPJ should not be checked in.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge


Sorry to disagree Peter, but the .xpj file should be checked in. It contains information regarding source control status, new ignored words, etc.

There is also an option to forcibly check in topics when you close the project in the Options | Version Control dialog box. I also strongly recommend using the Comment required field options in the Version Control pane unless your source control engine already requires them.

.MW

1 reply

A
Anonymous
May 18, 2011

Hi Roza,

Once user1 has checked-in the new topic, did user2 got the latest version of the project by clicking on the Get Latest option from the version control toolbar or the File menu ?

Thanks,

Aditi

A
Anonymous
May 18, 2011

Thanks for the response, Aditi!

We did indeed click "Get latest version" but we've discovered our problem had to be solved elsewhere. After testing RoboSource some more, we discovered that there are files (.fpj or .apj. or .xpj) linked to topics, snippets, etc. These need to be checked in as well. Before we just clicked the topic and selected "check in" and of course this only checks in the .htm file.

A
Anonymous
May 26, 2011

Just wondering, why do you recommend to use the required comments? Because we're only two people working on one project, I don't really see why this would be necessary. Also, we're working in the same office, so comments or remarks can easily be made face-to-face. But I am interested to hear why you recommend this, maybe we are missing something. Working with Version Control is new for both of us and we still encounter problems.

Thanks to all of you for your answers and thoughts!


Your work flow is, of course, up to you. I work with a much larger team. Commenting shows a measure of mercy to anyone who comes after you and might want to know what kinds of changes you made and why. That said, its been my experience that lots of comments are on the order of "Changed blah." Your mileage may vary.

.MW

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices