![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DXL Attribute Executes on Every Screen Refresh Topic Summary: Attribute DXL Refreshes When it Should Not Created On: 22-Sep-2004 18:17 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Louie, You were absolutely right about setting obj.attrDXLName to something other than null (""). In desparation last night, I set all "" entries to contain a space " ", and the problem went away. Then backed off until I found out which one was causing it. I ended up setting the value to "-1" so I could get the result I wanted, and now it is fine. There were several attributes that fell through the code and were reset to "". In that condition, DOORS seems to want to recalculate them every time you resize or move the window, click on a different object, move another window over the top of that window, etc. I don't think I understand why it would do that? But, I am happy I know how to avoid it now. Thanks also for the other tips. Richard | |
![]() |
|
I wonder whether anyone out there can help with a problem. The code below executes fine as a DXL attribute and does what I need it to do. The problem is that every time any screen refresh takes place in DOORS, such as just selecting an object or resizing the window, it appears to recalculate all the values. From what I read, Attribute DXL should only recalculate when the module is opened or you select Refresh DXL Attributes from the Tools menu. This constant recalculation makes the module difficult to work with. This Attribute DXL script is used to display up to 12 columns, each with 32 objects.
Is there something in this script that could cause the Attribute DXL to behave this way? Thanks in advance for any suggestions. Richard L-3 Communications Integrated Systems Greenville, TX |
|
![]() |
|
![]() |
|
Oops. Forgot to mention that AttrDXL also recalculates when the current value is null. If you change your last line to obj.attrDXLName = " " (a space) it should drastically reduce the recalculation. (Or do you want to set it to "0.0"?)
- Louie Nit-picks: [1] after your entire loop perhaps you should add: "if (isDeleted(o)) continue"; thus bypassing deleted objects in the other module. [2] using o."Object Text" gets the RAW text only, specifically not bold etc formatting and embedded OLE diagrams. That's probably what you want but maybe not. |
|
![]() |
|
![]() |
|
Louie,
You were absolutely right about setting obj.attrDXLName to something other than null (""). In desparation last night, I set all "" entries to contain a space " ", and the problem went away. Then backed off until I found out which one was causing it. I ended up setting the value to "-1" so I could get the result I wanted, and now it is fine. There were several attributes that fell through the code and were reset to "". In that condition, DOORS seems to want to recalculate them every time you resize or move the window, click on a different object, move another window over the top of that window, etc. I don't think I understand why it would do that? But, I am happy I know how to avoid it now. Thanks also for the other tips. Richard |
|
![]() |
|
![]() |
|
Oops. I also forgot to mention that early on we had tried commenting out the line
obj.attrDXLName = "" but that didn't help. So apparently if you don't set the value of the object at all, it has the same effect as setting it to null. I guess it has to be set to something! Richard |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.