![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Formatting tracked by history? Topic Summary: Created On: 19-Apr-2004 08:59 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Yes, changing display options does NOT affect history because it does NOT modify an object: it only changes how it looks to YOU. Yes, that means you may see an object differently than someone else. Notice that the display settings basically affect Font and Size based on object depth. This is similar to modifying your Windows Desktop size settings: DOORS looks different to you but doesn't change anything. But that's not the same as changing the BOLD/ITALIC settings within an object since DOES modify the object itself; and will generate History. - Louie | |
![]() |
|
Can anybody confirm our experience that changing the display options (font size displayed on the screen) affects history (DOORS 7)? We are making history dumps to Excel with every baseline, and since I needed to adapt display options for better readability during a recent meeting, I noticed that these richText noise appears in the history, showing that the attribute has changed. Not useful at all, in my view, as the content of the attribute is unchanged. Is this a bug or a feature?
This means the history dump script will need to (1) strip any history entry of richText (how is this done?) information and (2) compare if there is really a difference between OldVal and NewVal. Any views on this? - Pieter ------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
|
![]() |
|
In the mean time, we have stripped away the RTF information, but this then clearly shows OldVa; = NewVal, which raises the question: why is this done by DOORS? Is it because the strikethru, underlining, bold and Italics are RTF-stuff you want to trace with history?
------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
|
![]() |
|
You'll need to write a StripRT function to strip RT from the strings. In v6/v7 such a function features "RichTextParagraphs" where you get the rtp.text and separate them with a CR, but don't end with a CR. In v5 this function features "RichText" rt.text chunks, each optionally ending in a CR if rt.newline is true. The rt.newline function works INCORRECTLY in v6 (and presumably v7), so the same function will NOT work in v5 and v6.
I think History should record formatting-only changes: lets not let Telelogic decide what's an "important" change and what is not. Good luck with History. Many of the "parameter" only apply when the History.type is of a certain value: the OldVal and NewVal parameters are undefined, for example, when the type is "Create Attr". Be sure to check for type "modify" before accessing them. - Louie |
|
![]() |
|
![]() |
|
Thanks Louie,
We succeeded in stripping the RT, but will look into how it was done. Maybe your suggestion is a more proper way. And, yes, I agree with you on the point of what is important. After some reflection we decided to doe the test ourselves if the content jas changed. If not, a Boolean will reflect this information. Another question: I notice in DOORS 7 (compared to 5.2) that they have added a function in the history DB that adds "red lining" showing the differences. Does anybody know a DXL function that does this, or is it to be developed by the user? - Pieter ------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
|
![]() |
|
There is a "diff" function for generating redlined text -- it's in the DXL manual for version 7.0. It takes three Buffers -- two for the input and one to put the result in.
On the original question, changing display options in itself will not affect history. I've just changed my display settings, opened a module, opened an object for inplace editing, and then clicked elsewhere without making a change. The object isn't marked as being modified and I can close the module without getting a warning about saving. But I can imagine a situation where the RTF markup might change in an invisible way. Judith |
|
![]() |
|
![]() |
|
Thanks Judith,
Maybe the cause-and-effect relationship is not so clear in the example I described above. SHould look closer at what caused the RT to be included. In my perception, the display options was the only changes applied, but maybe there is something else. Fact remains, that I have OldVal <> NewVal, where the delta is only in the RT (OldVal has no RT, NewVal has it). Will try to apply the diff function. ------------------------- Pieter de Waard www.nhindustries.com |
|
![]() |
|
![]() |
|
Yes, changing display options does NOT affect history because it does NOT modify an object: it only changes how it looks to YOU. Yes, that means you may see an object differently than someone else. Notice that the display settings basically affect Font and Size based on object depth. This is similar to modifying your Windows Desktop size settings: DOORS looks different to you but doesn't change anything.
But that's not the same as changing the BOLD/ITALIC settings within an object since DOES modify the object itself; and will generate History. - Louie |
|
![]() |
Telelogic DOORS
» Defect/Issue Tracking
»
Formatting tracked by history?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.