![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Having issues with block and release... Topic Summary: Created On: 25-Oct-2007 22:08 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Did a test and found that when you issue 'release', you get two DXL threads; one continues after the 'release' and the other picks up after the 'block'. I found that VERY curious. Anyway, two DXL threads are dangerous and should be avoided; therefore putting 'release' at the end of the function sounds like a good idea. I think that when you 'release', you automatically close the dialog. Therefore, trying to 'destroy' it afterwards may cause problems. At the bottom, I don't think you want to call 'closeDialog' when in fact you never blocked the dialog, since the 'release' command inside that function is likely to get very confused. I'd just 'destroy(win)' at that point and be done with it. Either that or move your '!isRead' line to the top of that function, and don't bother defining the dialog unless you intend to block it. Try the attached ditty. Notice when you push the 'applyClose' button you get two ACKs, but it you 'close' you only get one. - Louie | |
![]() |
|
I've got the attached script which basically enters a Change Request number in all objects that have been modified during that particular session when the user saves the module. That part of the script works...... ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Did a test and found that when you issue 'release', you get two DXL threads; one continues after the 'release' and the other picks up after the 'block'. I found that VERY curious. Anyway, two DXL threads are dangerous and should be avoided; therefore putting 'release' at the end of the function sounds like a good idea.
I think that when you 'release', you automatically close the dialog. Therefore, trying to 'destroy' it afterwards may cause problems. At the bottom, I don't think you want to call 'closeDialog' when in fact you never blocked the dialog, since the 'release' command inside that function is likely to get very confused. I'd just 'destroy(win)' at that point and be done with it. Either that or move your '!isRead' line to the top of that function, and don't bother defining the dialog unless you intend to block it. Try the attached ditty. Notice when you push the 'applyClose' button you get two ACKs, but it you 'close' you only get one. - Louie |
|
![]() |
|
![]() |
|
When using block/release, I have always written my programs to not do anything after the call to release since, from the DXL manual description, I thought once the call to release was made, the program jumped back to the block call and continued execution, like a return. So I call destroy right after block.
Seems to have worked well for me so far. ------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
Thanks Louie and Dave, that did the trick.
I think I have to go look at another script I used block in. Haven't had issues with it yet, but need I think I destroyed the box after the release in that one too. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Having issues with block and release...
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.