Double note sizes

[DavidM]

Hi,
I have created this related shape script example straight from the example page. Everything works as it should once I save and re-load and set the features for realized to be visible.

However , the note when assigned is exactly twice the length of the text. This means that when I have  10 lines of text, I have 20 lines of text with 10 of them being blank.

Is this a feature I have to live with, or is there anything I have to do?



I thought maybe making a stereotype  of the note and re-sizing, but it seemed overkill, plus I want to add pin features and I'm not sure how that is done in MDG.

Any help would be appreciated.

Thanks

shape RelatedElement { // add Child Compartments to the parent.
 
     if(HasProperty("Connector.Type", "Realization"))
    {
            
           if(HasProperty("Element.IsSource"))
            {
               SetCompartmentName("Sub Capabilities");
               AppendCompartmentText("#element.NAME#");
               
            }
       }
 }

[qwerty]

How is that script related to the element's notes? I can't follow.

q.

[DavidM]

Hi Qwerty.

What I am doing is trying to populate a Note, connected to an element, with the contents of the element realized components.

Say for example we a logical element called Bus. From that element we realize it to other elements called Double decker bus, tour bus, city bus.

When I create a note and assign it to an element feature, I would expect the note to contain
Double Decker bus
Tour Bus
City bus using the attached code on the element Bus.

This works well, but what happens, is the note is substantially larger than the 3 rows consumed. i.e. there is a lot of "dead space" beneath them.

I cannot re-size them, it ignores me (I call it the teenager syndrome ;-))
So I am left with notes much bigger than the text they contain.

Now image I have an element of say 14 realized elements, I have 28 rows, 14 populated and a lot of distracting space taken up in the diagram.

It looks very, very messy and not practical.

Hope this makes sense.

[Geert Bellekens]

David,

So for each connected element you make a new compartment?
That might be the problem.

Have you tried adding them all in one compartment?
I can imagine that EA automatically adds some whitespace above and below compartments, which would result in something you described.

If that doesn't work, maybe you can try it without a compartment, using the Print or PrintWrapped functions.

Geert

[KP]

There's nothing wrong with your shape script. It works fine on my machine. (Sorry, not that helpful)

[KP]

OK, now I can reproduce it. It seems to only happen if the last line of text has spaces in it. It upsets the word-wrapping somehow. If we can reproduce it, we can fix it...

[Paolo F Cantoni]

OK, now I can reproduce it. It seems to only happen if the last line of text has spaces in it. It upsets the word-wrapping somehow. If we can reproduce it, we can fix it...

But only if someone posts a bug report?

Paolo

[DavidM]

A sorry guys,
Been away on holiday.
To try and answer all the questions
- No I am only doing this in one shapescript compartment - the example given is from the sparx web page, and if the compartment already exists it is intelligent enough t ore-use.

Blank last line - is that actually in the code of if a blank line is somehow being generated in the list of dependencies? I shall check out my examples, but I don't recall having a blank line.

If it is a bug - do I need to create a bug request as suggested to initiate getting it fixed?
Thanks,
David

[davidson]

Can I just check below.

 if(HasProperty("Element.IsSource"))
            {
               SetCompartmentName("Sub Capabilities");
               AppendCompartmentText("#element.NAME#");
               THIS BLANK LINE CAUSES THE PROBLEM?
            }

[qwerty]

The RelatedElement seems to be quite buggy (see also http://sparxsystems.com/forums/smf/index.php/topic,35992.0.html. http://sparxsystems.com/forums/smf/index.php/topic,31032.msg224960.html#msg224960 and others). I tried this feature once again and this time even did not manage to show up in V13. So I'd recommend to send a bug report (bottom right of this page; Support section).

q.

[davidson]

I just tried this taking out the space and it still produces the large note.

BTW - I am using a shapescript (hence the notes to describe what is in the compartment) for the original icon.

[KP]

Can I just check below.

 if(HasProperty("Element.IsSource"))
            {
               SetCompartmentName("Sub Capabilities");
               AppendCompartmentText("#element.NAME#");
               THIS BLANK LINE CAUSES THE PROBLEM?
            }

No, I meant the last line of text being passed into AppendCompartmentText(), i.e. the last value of #element.NAME#, had spaces in it. After I reproduced the issue, I took the spaces out of the element name and the note displayed correctly. This leads me to believe it's a problem with the word-wrapping.

[davidson]

Ah Yes - that seems to be the issue. Thanks
Pity I know what the problem is now, but I need spaces.....

[davidson]

Further feedback on this erratic defect.

I changed the dependancy of one element to remove spaces. Saved it. Re-loaded it and re-sized it to the correct position and it worked.
Even when I put the spaces back in.

When I tried it on another however, it didn't work and wouldn't re-size, and no change was implemented.

[Paolo F Cantoni]

Welcome to EAUI...

Paolo