![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: "Module does not have a window" Topic Summary: what does this mean? Created On: 1-Aug-2006 16:40 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
When running a script on his computer, my boss receives a DXL error:
-R-E-DXL:
|
|
![]() |
|
![]() |
|
hi Matt, i had this problem some weeks ago and i found no answer, but a workaround: |
|
![]() |
|
![]() |
|
Hi Matt,
i had this problem on using "eXchange". The reason was a trigger installed in the database (in my case: show the mod-id in the status bar of the module window). Removing this trigger via dxl-script solved "my" problem. here two scripts from telelogic which may help: 1.) show triggers #### void dumpTrigger(string sMsg, Trigger t) { print "\n-----------------------------\n" sMsg ": name=" (name t) ", kind=" (kind t) ", level=" (stringOf level t) ", type=" (stringOf type t) ", event=" (stringOf event t) "\n" print "DXL code:\n" (dxl t) "\n" } Trigger t Project p = current Module m = current for t in database do dumpTrigger("Database trigger", t) if (!null p) { for t in p do dumpTrigger("(current) Project trigger", t) } if (!null m) { for t in m do dumpTrigger("(current) Module trigger", t) } #### 2.) remove "my" trigger #### Trigger t for t in database do { if (name(t) == "modid") delete (t) } #### both scripts came from telelogic-support I hope this will help Peter |
|
![]() |
|
![]() |
|
Too bad he didn't write down the line of DXL code associated with that error.
I've never seen it, but it feels to me as if one is using a Module handle after the module has been closed. The Handle itself retains a valid non-null value for a short time after the module is closed (perhaps half a second). I doubt you wrote the script incorrectly, unless you auto-close all the modules you found but then presume to go back to the original 'current' module; which you forgot gets closed in the body of the script. In the mean time, tell your Boss that he's haunted and he should leave the DOORS work for trained profesionals only. - Louie |
|
![]() |
|
![]() |
|
Louie
I enjoy your humor with your posts. Keep it up. ![]() Matt This is probaly not related but does your boss and you have the same DOORS permissions? Again, probaly not the issue but it didn't hurt to ask. ------------------------- pete.kowalski(at)motorola.com |
|
![]() |
|
![]() |
|
I believe the truth came out that he had been playing around with his triggers, and after we "fixed" them (reset them to what they were before said playing), we were able to eradicate the error. He does indeed have different permissions and actually an entirely different database (we run a local version for testing purposes), we ran it on a different computer using the same database and it worked, so again we believe the problem was involved with his tampering. I guess I should point out that he is not haunted, just not blessed with the same DOORS touch we have. ;-)
|
|
![]() |
|
![]() |
|
He must be 'blessed' with different DOORS touches than you. Negative 'touches' are called 'haunts', thus my comment. lol
|
|
![]() |
Telelogic DOORS
» DXL Exchange
»
"Module does not have a window"
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.