Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic SYNERGY (steve huntington)
Decrease font size
Increase font size
Topic Title: Type Definitions are broken - how to make good??
Topic Summary:
Created On: 2-Aug-2004 13:51
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Russ Braithwaite, on Wednesday, August 4, 2004 3:52 PM

Answer:
What I have in my ccm.user.properties file is (for the batch typedef):

windows.tool.edit.batch=c\:\\progra~1\\textpa~1\\textpad "%file1"

This works OK & was inherited from when we had 6.2 so I haven't checked if it works with the full path in long form - but I assume it would. To set this as the default editor I think, from memory, you need to set windows.tool.edit.ascii & windows.tool.view.ascii for the default viewer.

HTH.
 2-Aug-2004 13:51
User is offline View Users Profile Print this message


David Lynam

Posts: 25
Joined: 22-Jun-2004

CM S. Version: 6.2

Hi,

We've recently upgraded veryone's PCs, and the location of the text default editor (TextPad 4) on everyone's PC has changed from where it was on the old PCs.
Not a problem I thought - I just need to change path to the new .exe in the the type definition options.

Unfortunately, when we try and open any file, vis CM Synergy, that should use Textpad, they are empty and come up as "Document 1" in the editor's title bar, rather than their name.
They always open as blanks whether or not I have default_edit_cmd defined as the viewer/editor (although the editor changes if default is used).
Opening the same files from the work-area is fine.

Anybody know if I'm missing something?

Edited: 2-Aug-2004 at 13:53 by David Lynam
Report this to a Moderator Report this to a Moderator
 2-Aug-2004 14:00
User is offline View Users Profile Print this message


Russ Braithwaite

Posts: 41
Joined: 13-Jun-2003

Just checking the obvious - but do you have the %filename at the end of the edit command? It sounds as though this is not being interpreted (if present) for one reason or another. If it is there, are any messages appearing in ccm_ui.log when someone tries to open a file through the GUI?

-------------------------
Russ Braithwaite
Software Configuration Management
Friends Provident
Report this to a Moderator Report this to a Moderator
 2-Aug-2004 15:02
User is offline View Users Profile Print this message


David Lynam

Posts: 25
Joined: 22-Jun-2004

Thanks for the speedy reply.

It's defined like this: "C:\Program Files\TextPad 4\TextPad.exe %filename".

I've had a look in the ccm_iu.log found in "C:\cmsynergy\<my login id> and there's nothing in there.
Nor is there anything in the file that's found at C:\


I've redefined the text editor in the ccm.ini file top be Textpad, and altered the type def to use "default_edit_cmd" - but I still get the same problem.
It's not just local to me, regular users get the same prob.

Starting to get bizarre now as it used to work ok, is there any little tweak that might need to be made to an .ini file or something like that?!

Edited: 2-Aug-2004 at 15:44 by David Lynam
Report this to a Moderator Report this to a Moderator
 2-Aug-2004 16:11
User is offline View Users Profile Print this message


Russ Braithwaite

Posts: 41
Joined: 13-Jun-2003

Not sure what else to suggest; you can quickly test any changes to a type-specific editor or viewer using the CLI, e.g.:

ccm set ascii_gui_edit_cmd "C:\Program Files\TextPad 4\TextPad.exe %filename"

& a similar command for the default edit command, i.e.: ccm set text_editor "..."

But that works fine when I do it.

A thought occurs to me: we are on 6.3 now but under 6.2 was it not the case that you needed to specify the path & name of the executable in Windows 8.3 format under some circumstances?



-------------------------
Russ Braithwaite
Software Configuration Management
Friends Provident
Report this to a Moderator Report this to a Moderator
 2-Aug-2004 16:57
User is offline View Users Profile Print this message


David Lynam

Posts: 25
Joined: 22-Jun-2004

A colleague mentioned that, but said it was only for the old Continuus, and it was if there were spaces in the path, if I remember correctly.
In particular, they said it for MS Word, but I'll have a go changing it, as that's the only thing that's changed with the new machines!

Will let u know what happens (cue drum roll....)
Report this to a Moderator Report this to a Moderator
 4-Aug-2004 12:03
User is offline View Users Profile Print this message


David Lynam

Posts: 25
Joined: 22-Jun-2004

Well, a twist to events is that explicitally defining in a user's ccm.ini file, the text_editor and text _viewer, they are able to open the files correctly from the Classic Interface.

However, the Developer's interface isn't playing ball.
Does anyone know if I will have to go through defining the ccm_exec for each type, rather than just leaving it in for ascii & binary?
OR, will I have to put in the path to our text editor?
Report this to a Moderator Report this to a Moderator
 4-Aug-2004 12:25
User is offline View Users Profile Print this message


Russ Braithwaite

Posts: 41
Joined: 13-Jun-2003

Answer Answer
What I have in my ccm.user.properties file is (for the batch typedef):

windows.tool.edit.batch=c\:\\progra~1\\textpa~1\\textpad "%file1"

This works OK & was inherited from when we had 6.2 so I haven't checked if it works with the full path in long form - but I assume it would. To set this as the default editor I think, from memory, you need to set windows.tool.edit.ascii & windows.tool.view.ascii for the default viewer.

HTH.

-------------------------
Russ Braithwaite
Software Configuration Management
Friends Provident
Report this to a Moderator Report this to a Moderator
 4-Aug-2004 15:52
User is offline View Users Profile Print this message


David Lynam

Posts: 25
Joined: 22-Jun-2004

Hullo again!

Finally got it sorted - I noticed from one of the TL help files and your post that I'd only been doing 1 back-slash, and this was messing it up!
I'm going to do as you suggested in the ccm.user.propertiesfile, for each file type, and have the users paste it into that file & the ccm.ini file too.

This is all rather confusing as it worked perfectly and without any need for this, before we moved to XP, all I had to do was define the Tye Def's correctly in the GUI!


Thanks for your help, Russ.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic SYNERGY forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 15:34.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.