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: Comparing Session date with other Modified module dates
Topic Summary:
Created On: 19-Nov-2002 15:16
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.
 19-Nov-2002 15:16
User is offline View Users Profile Print this message


Richard harkness

Posts: 13
Joined: 24-Oct-2002

Hi,

Spent a while on this, and am once again turning to you guys...

I have the following layout DXL code... see attachment.

The problem I have is in the setting (getting) the modified date of the linked module using the line...

if (!null parentModName){dateModified=modified(create pName)}

The code generates a dxl error...

-R-E- DXL: <Line:40> null Stat parameter was passed into argument position 1
-I- DXL: <Line:6> execution halted

Any help would be appreciated.
Report this to a Moderator Report this to a Moderator
 19-Nov-2002 22:52
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I'm feeling grouchy today...

Try using comments.

Lets assume line #7 is "if (dateModified >...".

Line #4 correctly gets the full module name. Line #5 correctly gets the short module name, although I have no idea why you would want to do that.

Line #6 seems to be "create"ing a "Stat" handle of a "file" with the same name as the module, and then figuring out the last time the "module" was changed? If so, there is no system file name with the same name as the module. The "create" command will return null (since there is no file named pName), and this will explain (I guess) your errors. Instead, open the parent module and retrieve the modParent."Last Modified On" module attribute.

Line #7 needs to check for a null dateModified or it will fail if ever you get line 6 to work.

Skip the close and open at lines 11 and 12: maybe the parent is already open exclusive and visible; so why close it? Also, when you do this in a Layout you will end up closing and opening the module for EACH object displayed, and you will be staring at a locked up DOORS all afternoon.

Move is-the-parent-module-OK checks lines #15-#17 up.

After line #18, insure the target object handle is not null, and optionally not deleted.

History Loop line #19: I don't recall the order in which history entries are retrieved with the loop. To get the latest "modified" history you will need to either [a] Abort when you find the first one since that is the "latest" one, or continue through the loop as you are doing now.

Anyway, consider the attached code.

- Louie
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 0 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 0 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.