I am currently recreating a bunch of class diagrams from Rational Rose in Enterprise Architect, and as a result from the converting, almost all of the classes have tags like {root}, {leaf}, {root,leaf}.
Is there any way I can remove all of these without having to go though every class and unchecking the Is Root and Is Leaf checkboxes?
In the Diagram Properties dialog, there is an option "Show Element Property String". You can switch this off for each diagram.
Alternatively, you could export your model to XMI, open it in a text editor, do a search-and-replace to remove all occurrences of isroot="true" and isleaf="true", and then re-import the XMI.
Related
I am trying to determine a package for an data element, or domain, or whatever via Eclipse ADT, but have no luck. I'm doing usual object search via project search (Ctrl-Shift-A), and both Global search (Ctrl-H), the result is the same.
I see domain properties window
and it has no clue about what package it is.
What I've tried so far:
Using filters in project search bar, callable via Ctrl-Space
Package filter does not help, it lists all packages, not the relevant ones, where this domain was found. Picking each and every package will take infinity amount of time, because the hierarchy is huge.
Pressing "Link with editor" button
For some reason it doesn't work, should it with DDIC objects? When I press it with domain opened right-side, just nothing happens. In the help and e.g. here they describe it should open the object in the left within hierarchy.
Is it something broken with my ADT or this button doesn't work with DDIC objects?
P.S. It is ABAP Cloud trial system, if that matters.
Package can be seen in Properties tool (see the bottom part of the screenshot below)
How can I set PhpStorm file structure view to show inherited members by default (or change key binding from Ctrl+F12 to show)?
The question pretty much says it all.
I configured file structure to show up with Ctrl+Alt+S, but cannot change the default setting for show inherited and can't change the keys either.
Is there a file, where default non editable configurations are in?
For example there is an xml file under PHPStormRoot\config\keymaps
What would the action be for that?
Is there a plugin for more configurations?
Should I consider writing a plugin myself (would I be able to change such things)?
I found that if you remove the other configurations(ctrl+F12) for opening file structure, show inherited members becomes your keybinding(ctrl+alt+S).
However it can be buggy, won't open until you re open the IDE.
Also you will be delighted to know that if the method you are looking for doesn't exist it will automatically search from inherited members too.
I also removed f12 from my keymap at PHPStormRoot\config\keymaps\$YOURCONFIGFILE.xml
EDIT: Show extra info
I am trying to add a simple windows form to my VB.Net project. I have used the designer to design the form how I want it with buttons, a text box and a Timer. The problem is when I try to view the code, there is only an empty class that looks like this:
Public Class MCastMain
End Class
I have set the application type to a windows form application in the project properties, and I have made a successful build of the application since doing so. I have been scrawling the internet and this forum for about half an hour now and I can't find one other person who is having this problem, nor can I find a tutorial that mentions any special steps that must be taken beyond what I have done. This is the first project I have done in Visual Studio.
I know this is probably stupid simple, but I have no idea what to do. Any help is appreciated as always.
Forms comes as partial class meaning the code is separated in two files.
The "empty" code you shown is from "mcastmain.vb" (if the file is named as the class).
With that one there is a (probably hidden) file "mcastmain.designer.vb" file which contains the generated code by the designer ; and is not meant to be modified (as any designer change will rewrite the file).
To show the hidden files you have to look in the solution explorer on the button on it's top there should be a "show all files" button. (it may be possible to do the same via the menu but I don't have VS right there to be sure where)
For each model element, there is the option in EA 10 to create internal requirements, constraints and scenarios. All of them end up in reports if you use the pre-defined Basic Template.
However, if you select "structured specification" instead of the default "description" text field for a scenario, then I end up with the steps of the structured specification being ignored in the report output.
How can I have them included in reports?
It sounds like you need to create your own reporting template. This may seem a bit daunting first time out and the template editor is pretty ornery, but luckily you can use an existing template as a starting point.
Hit F8 to bring up the Generate Documentation dialog, then select the Templates tab. Click New, specify a name and select a template you like to be copied. Don't bother with a template group, and leave the fragment checkbox unchecked.
In the editor, scroll down about halfway (assuming you selected to copy the Basic template) and locate the yellow scenario > tag.
Now in the checkbox tree on the left, scroll down do Package - Element - Scenario. Note that Scenario is checked, but Structured Scenarios is not. Check it.
In the editor, note the new structured scenarios > tag. Remove the right-click-to-insert text, then right-click and select Insert Field, then State etc.
It's more than a little fiddly, but if the Basic template is good enough to begin with you should be able to add the structured scenarios with a minimum of effort.
For more information, see the help file under Reporting - RTF Documents. Note that the individual fields aren't listed in the help file, you need to open up the template editor to see what specific information you can extract to your report.
(I'm something of an Eclipse newbie, so apologise for any dumbness on my part...)
I have a number of editors (derived from IEditorPart) in my RCP app, and a requirement has arisen that one particular editor needs to be also available in a modal dialog box (along with some extra controls) opened by one of the other editor classes. The editor to be embedded consists of the main viewer control, toolbar, and a couple of dozen helper classes (label providers, comparators, etc).
The options before me appear to be:
Find a way to put an editor area, IWorkbenchWindow-style, into a (JFace or SWT) Dialog.
Not had much luck searching for how to do this
Create a new WorkBenchWindow with a Perspective that just the editor area visible, and no views. Make this modal.
On trying this, the new window seemed to inherit things (menus etc) from its parent window.
Refactor the editor in question so all of it now resides on a single control, then embed this control in both the editor and the dialog.
Potentially time-consuming, given the number of places the helper classes refer back to the main editor object.
If it turns out that this is a truly perverse and anti-idiomatic thing to want to do, in Eclipse terms, can you suggest a wiser course of action?
Thanks
EditorParts are meant to be inside workbenchwindows. There is a lot of code that depends on this behaviour. So I would suggest not to do (1). If the result is acceptable (a workbench window, which is modal), the easier way is to hang on to (2).