![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Rich text issues with DOORS 6 Topic Summary: Created On: 18-Jul-2003 14:24 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Pete, thanks for the feedback. From DOORS Technical Support, Case #NS2033311: Development has confirmed that this was broken in DOORS 6, but that it does work in DOORS 7. However, they were unable to provide me with a workaround. | |
![]() |
|
In using DOORS 6, it looks like the rich text features have been broken. In particular, I'm using the loop which parses all the rich text from a string. Specifically, the following code used in DOORS 5 and DOORS 6 should produce identical results but does not.
string s="This is a {\\b test} of the {\\i rich text} capabilities." RichText rt for rt in s do { if(rt.bold) print "(bold)" if(rt.italic) print "(italic)" print "\t" rt.text "\n" } Using DOORS 5, you get this nicely formatted result: This is a (bold) test of the (italic) rich text capabilities. But in DOORS 6, it looks like this: This is a (bold) t (bold) es (bold) t o f the (italic) rich (italic) tex (italic) t c apabilities. Has anyone else encountered the same problems? Can someone run the code in DOORS 7 to see what the results are? Thanks, Dennis |
|
![]() |
|
![]() |
|
This is what I receive from running the code in DOORS7,
-- This is a (bold) test of the (italic) rich text capabilities. -- ------------------------- pete.kowalski(at)motorola.com |
|
![]() |
|
![]() |
|
Pete, thanks for the feedback.
From DOORS Technical Support, Case #NS2033311: Development has confirmed that this was broken in DOORS 6, but that it does work in DOORS 7. However, they were unable to provide me with a workaround. |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Rich text issues with DOORS 6
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.