![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Change Filtering Defaults? Topic Summary: Created On: 13-Sep-2004 17:56 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: As far as I know these ARE the default values when the module is opened. However, its possible that the default view for the module may deliberately change these advanced settings. The problem with that is this: if the next view loaded does NOT set or remember the settings then the display inherits the settings from the earlier view. Thus, resetting these things needs to be done on demand rather via an open trigger. That's why I've got a "SetPureFilter.dxl" available from a addins pulldown in all my modules. An alternate solution is to disallow a view from ignoring these settings: the Advanced view "Filter table contents", "Filtered objects' ancestors", and "Filtered objects' descendants". You can realistically create some "StandardizeAllViews.dxl" that loads each view, queries the settings and queries these view commands, and if the view doesn't remember, then set the corresponding display and set the flag, and resave the view. - Louie | |
![]() |
|
Is there a way to change the defaults in the Filter... window? I would like to have "Show ancestors" selected by default. The dxl code is compiled or encrypted, so it's not a simple change. Has anyone tried to do something like this?
Thanks! Shawn ------------------------- Shawn Stepper shawn.e.stepper@wellsfargo.com |
|
![]() |
|
![]() |
|
Hurray!!! Someone finally asked. I was so PROUD of myself for figuring this one out.
ancestors(false) descendants(false) filterTables(true) These act just like the buttons on the Filter Dialog; but you'll have to reload the filter dialog to see them updated. In fact, I've got these three in a simple "SetPurFilter.dxl" script in the module-menu, and advertise to the ignorant masses that when they run a filter and don't get what they expect, run this SetPureFilter and see if it clears it up. The real problem is that some views have these set or reset in the view. if the next view loaded doesn't care, these settings stay set and that's REAL annoying: load a view with a filter and don't get what you expect. - Louie |
|
![]() |
|
![]() |
|
Thanks Louie!
The only problem with this is that it is module specific. I was hoping to do it more globally. Maybe it can be done with a trigger, when a module is opened? I'll try it... ------------------------- Shawn Stepper shawn.e.stepper@wellsfargo.com |
|
![]() |
|
![]() |
|
As far as I know these ARE the default values when the module is opened. However, its possible that the default view for the module may deliberately change these advanced settings. The problem with that is this: if the next view loaded does NOT set or remember the settings then the display inherits the settings from the earlier view.
Thus, resetting these things needs to be done on demand rather via an open trigger. That's why I've got a "SetPureFilter.dxl" available from a addins pulldown in all my modules. An alternate solution is to disallow a view from ignoring these settings: the Advanced view "Filter table contents", "Filtered objects' ancestors", and "Filtered objects' descendants". You can realistically create some "StandardizeAllViews.dxl" that loads each view, queries the settings and queries these view commands, and if the view doesn't remember, then set the corresponding display and set the flag, and resave the view. - Louie |
|
![]() |
Telelogic DOORS
» Administration
»
Change Filtering Defaults?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.