Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: print of "Object Text" differs for objects with OLE
Topic Summary: OLE object print problem
Created On: 10-Jan-2005 21:52
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
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 Stuart Barr, on Tuesday, March 8, 2005 7:16 PM

Answer:
Thanks Louie,

You've more or less hit the nail on the head. Thanks for the explanation.

I was forced to make a work-around in my scripts, to test if oleIsObject. If so, I checked to see if there was a trailing " \n" (space, nl) in "Object Text", and then forcibly stripped it.

The scripts are now working as before in DOORS 5 now.

Regards,
Stuart
 10-Jan-2005 21:52
User is offline View Users Profile Print this message


Stuart Barr

Posts: 4
Joined: 17-May-2004

I've noticed a difference between DOORS 5.2 and 7.1, regarding the handling of object text.

I've an object that contains some plain text along with an embedded OLE object (bitmap file).

I find that a newline is automatically appended after the text in 7, which was not there in 5, causing crash and burn of some of my scripts... :-(

The following trivial code highlights the difference:

Object o = current Object
string otext = o."Object Text"
print "**START**" otext "**END**"


Result on DOORS 5.2:

**START**Protected Terminating Circuit Creation Wizard initial dialog**END**


Result on DOORS 7.1:

**START**Protected Terminating Circuit Creation Wizard initial dialog
**END**

If the object does not contain an OLE object, then there's no problem.

I'd be interested in hearing whether this is really a problem, or whether I've made an error somewhere.

Thanks,
Stuart
Report this to a Moderator Report this to a Moderator
 11-Jan-2005 14:20
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

Strange, I just tested this and I don't get the same results. It works fine for me. I do not get an extra carriage return when the object text contains OLE objects.

I am using DOORS 7.1 with patch 6. Build Number 71132.


-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
 8-Feb-2005 06:01
User is offline View Users Profile Print this message


Stuart Barr

Posts: 4
Joined: 17-May-2004

After further analysis, this problem is only seen on DOORS objects migrated from DOORS 5.2 to 7.1; new OLE objects entered in 7.1 don't exhibit the same problem. Apparently this is "not a bug" according to Telelogic, and was fully intended with the extensions to rtf support in 6.0, and will not be addressed by Telelogic.

Bottom line, I have to change my scripts to handle this...

Thanks for taking a look guys,

Regards,
Stuart.
Report this to a Moderator Report this to a Moderator
 8-Feb-2005 19:12
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I don't see where Telelogic has a real option. v5 OLE's were NOT embedded in the Object Text, they were associated with the Object itself and were displayed in the MAIN column. Displaying necissarily meant adding a EOL to the apparent end of the Object Text. When migrating to v6 the OLE in the object was appended to the end of the Object Text. If they didn't also append an extra EOL then the displayed main column would NOT look like it did in v5; it would often look odd since the OLE would be appended to the end of the last line.

So migrating v5 to v6 objects with OLE's meant appending an EOL and then the OLE.

Are you comparing stuff to insure it migrated? If so, consider the following:
if (oleIsObject(objV5))
......TextV5 = objV5."Object Text" "\n"
else TextV5 = objv5."Object Text"

- Louie
Report this to a Moderator Report this to a Moderator
 8-Mar-2005 19:16
User is offline View Users Profile Print this message


Stuart Barr

Posts: 4
Joined: 17-May-2004

Answer Answer
Thanks Louie,

You've more or less hit the nail on the head. Thanks for the explanation.

I was forced to make a work-around in my scripts, to test if oleIsObject. If so, I checked to see if there was a trailing " \n" (space, nl) in "Object Text", and then forcibly stripped it.

The scripts are now working as before in DOORS 5 now.

Regards,
Stuart
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 0 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 0 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.