![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Progress Bar hidden behind Modules in DOORS 8.1 Topic Summary: Created On: 14-Nov-2006 14:14 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello!
I am porting a DOORS 7.1 script to DOORS 8.1 The script shows a dialog box and a progress bar. During the script run various modules are opened with read(mod, true) and the progress bar shows the progress of the operation. All was fine in DOORS 7.1, but in DOORS 8.1 the modules are placed over the progress bar, so that it is hidden. The dialog box is created with topMost(). Open the modules with read(mod, false) is not an option, because I have to do some things with views which will not work if the module is not visible at all. Doing a raise() in the dialog box does also not what I want, behause it raises the dialog box and not the progress bar. Best Regards, Ludwig Weinzierl |
|
![]() |
|
![]() |
|
Have you tried creating the Progress Bar dialog Box using the topMost function
(page 431 of the dxl manual). This would ensure the dialog box is always on top of any opened modules.
|
|
![]() |
|
![]() |
|
Whoops sorry You did use the Topmost function, another trick we use , is that unless you really , really need to see what is goining on in the modules as the code executes open them with the display flag set to false. The Progress bar should be left on top and visible.
At the end of the scipt run just reopen the modules visible to see the results.
We have found considerable performance improvements by only displaying the module when you need to....
|
|
![]() |
|
![]() |
|
Two things come to mind:
One involves using 'raise (dialog_box)' straight after opening the module to bring the dialog box and its progress bar back to the front. The other is that, in their infinite wisdom, Telelogic have introduced a bug to DOORS 8... ------------------------- Paul dot Tiplady at TRW dot com TRW Automotive |
|
![]() |
|
![]() |
|
Write your own progress bar wrapper function.
I have done this in the past so that I can have a progress bar for functions that do not have a dialog box. Basically, create a simple dialog "floating" and add a progress bar to it! ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Thanks Tony,
I am not sure if I get you right here. Is there a way to use the progress bar without a dialog box? What I currently do is to create a dialog box with DB_ProgressBar = create("bla", styleCentered | styleFloating ) and add a progress bar. Then I open some modules which must be visible for various reasons. In DOORS 7.1 the order of the elements on the screen is like this (back to front): Dialog Modules Progress Bar This is exactly what I want. In DOORS 8.1 the order is like this: Dialog Progress Bar Modules Doing a raise on the dialog box results in this order: Modules Dialog Progress Bar This is not an option because it lasts only until the next module operation and doing a raise on every update of the progress bar results in terrible flicker. Besides that I dont like the Dialog Box visible behind the progress bar. It is not only that a progress bar is useless if it is not visible. Even worse is that you can not get hold of the cancel button on the progress bar if it is behind the modules. Ludwig Weinzierl |
|
![]() |
|
![]() |
|
Try moving your read statement before the progressStart() function
ie.., Module m = read("test", true) progressStart(x, "Experiment", "Something", nos) provides different results than: progressStart(x, "Experiment", "Something", nos) Module m = read("test", true) |
|
![]() |
|
![]() |
|
Nope, sorry.
I do not know the modules I have to open beforehand.
I pondered about having a progressbar for each module but discarded that idea.
It would be to confusing, considering the number of moules processed.
Ludwig Weinzierl
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.