![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
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 |
![]() |
![]()
|
![]() 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 | |
![]() |
|
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 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 |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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. |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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 |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.