![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Copy OLEs in v6 Topic Summary: Created On: 16-Sep-2002 21:36 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: In DOORS v6 there is a new function RichTextWithOle, which you can use in the same way as the richText function as applied to attributes. So you can write string sourceVal = richTextWithOle objFrom.attrname objTo.attrname = richText sourceVal You can also do this with buffers instead of strings, which is more efficient. Judith | |
![]() |
|
In DOORS v5 you could copy "the" OLE in the object via:
. if (oleIsObject(objTo)) oleDelete(objTo) . if (oleIsObject(objFrom)) . { oleCopy(objFrom) . olePaste(objTo)) . } In v6 any text attribute can have lots of OLEs in it, so now I need to find a way to copy them. Even though I can "oleCount" them, and if >0 put the attribute in a column so I can "oleCopy" them, I cannot "olePaste" them at all into the correct position in the destination object. It appears there may be some sort of richText solution to this, but my feeble efforts at rich text manipulation and viewing have yielded the fact that the rich text knows nothing about the OLEs in the text. How can I copy OLEs with DXL in v6? - Louie |
|
![]() |
|
![]() |
|
Louie,
If you're going to cut/paste the OLE objects discretely from one DOORS object to another, consider using either an intermediary to store the ole objects (use a skiplist for example), or have your call recursively grab the object as an OLE object (that has the multiple OLE objects in it to begin with; and when you perform the paste operations within DOORS, it recognizes that the OLE object (with all the subobjects included) is actually a DOORS object and should paste it without making it an icon or package. Good luck. rg. ------------------------- rg. ![]() |
|
![]() |
|
![]() |
|
In DOORS v6 there is a new function RichTextWithOle, which you can use in the same way as the richText function as applied to attributes. So you can write
string sourceVal = richTextWithOle objFrom.attrname objTo.attrname = richText sourceVal You can also do this with buffers instead of strings, which is more efficient. Judith |
|
![]() |
|
![]() |
|
Yes, this richTextWithOle sure seems like it will do the trick.
Thanks. I'm too ignorant about this RichText stuff and am a little paranoid, but the test cases I ran seem to work. I guess I'll just automatically use this command for all "Text" attributes; the only ones that can contain an OLE diagram. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Copy OLEs in v6
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.