Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
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
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 1-Aug-2006 16:40
User is offline View Users Profile Print this message


Matt Hofferth

Posts: 16
Joined: 20-Jun-2006

When running a script on his computer, my boss receives a DXL error: -R-E-DXL:Module does not have a window I haven't been able to reproduce this error on my computer running the same script on the same project. The script in question loops through all items under a project and finds the formal modules. It reads the attributes "Last modified on" and "by" and takes the name, type, and this info and writes it into a .csv file for a very simple report. It reads the modules without displaying (if that helps) using the basic read command. Like I said, it works fine on my computer, but he wants an answer and I can't even regenerate the error. Any thoughts?
Report this to a Moderator Report this to a Moderator
 7-Aug-2006 08:35
User is offline View Users Profile Print this message


Thomas Langholz

Posts: 40
Joined: 20-Oct-2005

hi Matt,

i had this problem some weeks ago and i found no answer, but a workaround:
modify your loop so that the module is opened in a window. it will cost lots of performance but it works.
i think it is a bug within doors with current module or whatever.

i hope this will help

greez
thomas

Report this to a Moderator Report this to a Moderator
 22-Aug-2006 07:30
User is offline View Users Profile Print this message


Peter Huttenlocher

Posts: 3
Joined: 22-Apr-2004

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
Report this to a Moderator Report this to a Moderator
 22-Aug-2006 21:05
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

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
Report this to a Moderator Report this to a Moderator
 23-Aug-2006 13:53
User is offline View Users Profile Print this message


Pete Kowalski

Posts: 301
Joined: 7-Feb-2003

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
Report this to a Moderator Report this to a Moderator
 23-Oct-2006 23:05
User is offline View Users Profile Print this message


Matt Hofferth

Posts: 16
Joined: 20-Jun-2006

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. ;-)
Report this to a Moderator Report this to a Moderator
 24-Oct-2006 23:26
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

He must be 'blessed' with different DOORS touches than you. Negative 'touches' are called 'haunts', thus my comment. lol
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.