6
Replies
Welcome to our community
However, we have the following questions/concerns:
1.) What is the difference between the two selections?
When you double-click a topic to make edits, the option to Auto-select will cause RoboHelp to examine the topic code searching for a meta tag indicating what editor was used to create the content. If it sees Microsoft Word, RoboHelp will try and open Microsoft Word to allow you to make edits. If it doesn't find a tag, generally Windows Notepad will open.
If the option to "use default editor" is selected, the topic will open in RoboHelp's editor.
2.) Can we all share the same files without any issues (e.g. loss of data, formatting, styles, etc.) if we all don't have the same option selected?
The option is agnostic to file data. You should be fine.
3.) Should we have done something else to fix the initial problem?
Of course the question remains as to why things failed. But they do seem to be working now. So as long as things are working, I wouldn't sweat it.
However, your explanation rings alarms. I need to ask exactly what the process is for "sharing" the files? It doesn't sound like Source Control is in use. So how do you manage to keep from clobbering one another's work? And I'm assuming when you say the files are stored locally that it means you are simply opening the local copies to make edits, right? If not, you are walking in very dangerous territory.
Cheers... Rick 
| Helpful and Handy Links RoboHelp Wish Form/Bug Reporting Form Begin learning RoboHelp HTML 7, 8 or 9 within the day! |
Rick,
Thanks for your quick reply. Unfortunately, we do not have Source Control in use at present. Didn't quite get the needed IT support to manage this and not quite sure how to do this on our own. We simply make all of the necessary edits to the files on our hard drives and upload and download from the network as needed. Cumbersome I know - but it works for us....for now at least 
Hello again
Sooo, I've asked before and I'll ask again. 
What is the process you are following? It may be cumbersome yet work just fine as long as you are taking safeguards.I ask because I may have some suggestions to offer that will help.
Cheers.... Rick
| Helpful and Handy Links RoboHelp Wish Form/Bug Reporting Form Begin learning RoboHelp HTML 7, 8 or 9 within the day! |
Hi Karen
Okay, thanks!
Here's the deal. Let's say Karen, Bob and Andrea are sharing the project. Bob decides to make updates. Bob copies the files from the network to his PC and begins making edits. But during that time, Andrea decides she needs to make an update. She doesn't know Bob has control of the project and is making changes. So she makes her changes. But before she is finished, Bob finishes and copies his changes back. After, Andrea copies HER changes back. When Andrea is finished, her files totally blew away what Bob changed because when she copied the project it was in the same configuration as it was when Bob first copied it.
So my query was to see if you had any mechanisms in place to prevent such a scenario. Typically one would perhaps have the content inside a folder and would maybe rename the folder from say... "Project" to "Project-In Use". By renaming, it provides a clue that it's not a good idea to copy. Then after you make edits and copy back, you "release" by renaming from "Project-In Use" back to "Project".
In addition to this safeguard, I would also encourage tight communication. Before Bob makes edits, Bob sends an E-Mail to Karen and Andrea saying he is making edits. That's another safeguard to alert the other team members to leave things alone. After the edits are complete, Bob sends an "all clear" that alerts Karen and Andrea that they are safe to edit if desired.
Anyhoo, perhaps you are already doing this. If so, terrific! But if not, it warrants consideration in order to save some pretty major headaches, hair pulling and gnashing of teeth down the road.
Cheers... Rick
| Helpful and Handy Links RoboHelp Wish Form/Bug Reporting Form Begin learning RoboHelp HTML 7, 8 or 9 within the day! |
AdChoices