Messages

1

Suggestions and Requests / Re: 9.0 diagram enhancements

« on: November 03, 2011, 08:59:40 pm »

Effectively it seems the problem is that embedded elements cannot be selected via shift+click.  This also causes problems if you are wanting to select multiple elements via shift+click.  As a workaround in both cases you could consider making the background element not selectable (using the right click "Selectable" option).

There is an easier workaround for selecting multiple embedded elements, just hold the ctrl-key and click to select the elements.

2

General Board / Recording History XML File Example

« on: November 04, 2011, 02:34:32 am »

I'm looking for an example file of the recording history in the xml format. Are there any examples available? I was not able to generate one myself because of the missing jdk or visual studio installations.
I would like to generate a recording history file from my embedded target and use it to generate a sequence diagram. That would save me a lot of work documenting the code dynamic behaviour.

3

Bugs and Issues / State machine transition with multiple operations

« on: May 05, 2010, 07:48:28 pm »

I would like to asign multiple operations to the transition effect. But I can only select one operation as soon as I select the "Effect is a Behavior" checkbox. Is this behaviour intended or am I doing something wrong?

4

Bugs and Issues / State machine operations

« on: May 05, 2010, 08:44:54 pm »

I would like to define state entry operations.
I found that I can drag and drop an existing operation to a state on the diagram. But the operation is simply copied not referenced. Why can't I use operations from the model, just as in the transitions?
I see no reason why I should define new operations for each state. This behaviour makes state operations almost useless for any reasonable sized model. You can't reuse or organize operations, they are bound to the state

5

Bugs and Issues / Preprocessor Macros for C

« on: March 24, 2010, 09:12:52 pm »

I need to define some preprocessor macros for C , because the source code has some none ansi C constructs for interrupt handling.
The parsing fails because of these constructs.

When I open the "Preprocessor Macros" menu from the settings i can not select the C language from the dropdown and therefore also not define any macros.

Is there a reason why C language should not be available as selection?