![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Get the Link Source Topic Summary: How to get the object information from Start Link - functionality? Created On: 4-Nov-2004 12:52 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Ok, I've implemented my own "Make Link from Start" with using of the standard DOORS functionality "Start Link" with a choice of available link modules. I know, that 'callStdItem(linkCompleteFromItem)' is a hack ( ![]() I think, it is much more comfotable for a user to select a link module in the same 'flow' he selects the target object (for many different link modules). | |
![]() |
|
If I make a link start with "Link->Start Link" in a module, how will I get the source object (i.e. id & module name) from an other module?
I want to write my own link-utility and implement it in the context menu. Therefor, I need the selected source object to create the link. The internal funcs linkStartItem()/linkCompleteFromItem() handle these, but are internal! Many regards, Dirk. ------------------------- Dirk Plaschke |
|
![]() |
|
![]() |
|
Dirk,
I have implemented my own link functionality on the context menu. I replaced the callbacks associated with the "start link" and "Make link from Start" options so these now use my functionality. It all looks exactly the same to the user, except that they get a popup dialog to fill in after selecting "make link from start". You will require global variables declared in the top context to store the link start object, and ideally the user should be returned to the start object (i.e. it is the current object again) after completing the link. The only menu you cannot modify in DOORS is the popup that appears after a drag and drop event. There is also no way to capture the drag and drop event. So drag and drop linking has to remain as it is. My work around for this is to allow the users to do drag and drop linking as normal, and provide a menu option to "update" these simple links to the annotated ones which are created when using the popup menu options. The built-in functions you mention make use of global variables that are also hidden from us, I would be very cautious above using these. Better to use your own. ------------------------- Tony Goodman http://www.smartdxl.com Edited: 4-Nov-2004 at 15:02 by Tony Goodman |
|
![]() |
|
![]() |
|
Hi, Tony.
How you select the source object as marked by DOORS ? Is there any function to mark the source object with the same background color, or did you only 'setSelection()' this 'object? It's more convenience for the user, if he sees the selected object like DOORS standard function. An other question is, if it is possible to extend the context menu to show items according to the number of Links (i.e.). I think, it is not possible, because the context menu items will be build with the createItem()-function. and this function(s) (from formal.dxl) will be executed only once at DOORS-Start,or? Therefore it is neccesary to popup an separate dialog box (with the different items). Thanks. ------------------------- Dirk Plaschke |
|
![]() |
|
![]() |
|
I am not changing the background colour or detecting the object marked by DOORS. You cannot control this with DXL.
I am marking (remembering) the link start object explicitly myself. You CAN dynamically control availability of menu options on the context menu. For example, I have a menu option for editing outgoing links which is only available if there are outgoing links. You control menu availability using the mapping function which is the first parameter to the createItem function. The menus are "built" once at doors startup. This seems to be the case because new items added to menus do not show up until you restart doors. But the mapping functions are executed each time you open the module. Example mapping function attached that test for outgoing links. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Ok,
I've implemented my own "Make Link from Start" with using of the standard DOORS functionality "Start Link" with a choice of available link modules. I know, that 'callStdItem(linkCompleteFromItem)' is a hack ( ![]() I think, it is much more comfotable for a user to select a link module in the same 'flow' he selects the target object (for many different link modules). ------------------------- Dirk Plaschke |
|
![]() |
|
![]() |
|
Hi,
I also would like to execute some of my own DXL before executing the standard "linkCompleteFromItem", but I don't get the function callStdItem to work. How can I use it? And does it still work in DOORS 8.0? Edo |
|
![]() |
|
![]() |
|
There is an underscore missing. Try this:
callStdItem_(linkCompleteFromItem) ------------------------- Shawn Stepper shawn.e.stepper@wellsfargo.com |
|
![]() |
|
![]() |
|
This is awesome! Using this I was able to bind "Make link from start" to Ctrl-J. So helpful!
Next question - is there a way to clear the start of t link using a similar method? I tried callStdItem_(linkClearStart) as a guess but it doesn't work. Thanks! ------------------------- Shawn Stepper shawn.e.stepper@wellsfargo.com |
|
![]() |
|
![]() |
|
Sorry if I am stating the obvious, but the standard item is "linkClearStartItem", not "linkClearStart".
Are you using an editor that has syntax highlighting? If not I recommend Crimson Editor. I find this a great help, especially because I can never remember the exact names of these things. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Fantastic! Thanks so much!
I'm using NEdit, which does syntax highlighting, but I have manually created the list of functions/constants/etc, so it is not entirely complete. ------------------------- Shawn Stepper shawn.e.stepper@wellsfargo.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Get the Link Source
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.