![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Module handle null after edit() Topic Summary: Created On: 8-Jan-2009 23:13 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Module m = edit( "module name" ) or edit( "module name", false )
Most of the time this works. However, sometimes "m" is null. Why? Bob Beck beck@assurtech.com |
|
![]() |
|
![]() |
|
Off the top of my head, it could be a few things....
1.) The user running the DXL does not have edit privilege to that module 2.) Someone else has the same module open in shareable or exclusive edit mode, preventing you from opening the module in exclusive edit 3.) Incorrect module name and/or path Ideally, you should always add checks to your DXL for null Modules (and null Objects), as these result in DXL errors to the user. Although, that can be a tedious chore. |
|
![]() |
|
![]() |
|
I've got lots of DXL that plow through modules, and I can safely say that my DXL has opened module's invisibly for edit perhaps a million times. I've never noticed a case where the module actually opened yet the returned Module parameter was null.
If the return Module is null it means the module did not open. If the Module is not null, you should still use "if (!isEdit(mod))", to make sure its is Edit and not open Read or Shared. Of course, if you misspell the module name or you lack Read access, you cannot open it. Of course, if instead of an absolute path (e.g. /"MyProject/MyFolder/MyModule") you use a relative path (e.g. "MyModule") and you are not in MyFolder, you also cannot open the module. v8 DXL has the ability to bypass the "Its open by someone else, open Read?" message you get when your dxl tries to open a module edit; no doubt it is open Edit by someone else and your DXL is not opening it read. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Module handle null after edit()
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.