Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - basalt

Pages: [1] 2
1
Suggestions and Requests / Re: SSKeyStore tool
« on: September 10, 2008, 04:17:20 pm »
Jep, a server can solve the problem, but let us know if there will be a server available or another solution for the problem.

thx
george

2
Suggestions and Requests / Re: SSKeyStore tool
« on: July 14, 2008, 07:38:36 pm »
So I can see the need of this feature from much different people, so I hope Sparx will provide a good solution for people with a LOT OF licenses.

kind regards
basalt

3
Suggestions and Requests / SSKeyStore tool
« on: June 11, 2008, 04:25:17 pm »
Hello to all.
We use the "SSKeyStore" tool to manage 20 floating lizences. But we are not able to trace the high count of the lizences, so we are not able to know if there is the need to buy more lizences. So here is my questions:
Is it possible to log the number of current used lizences? Or is there any possibility to write a own program to do this?
thx
basalt

4
General Board / Re: Problem with "feature" full qualified tagged v
« on: October 23, 2008, 12:18:28 am »
thx for the info, i have post a bug report.
kr
basalt

5
General Board / Re: Problem with "feature" full qualified tagged v
« on: October 22, 2008, 09:42:36 pm »
Hi all

A new version --- a new retest of duplicate tagged values.
Tested version = 7.1.0 833.

After sync tagged values with profile, no duplicates are there anymore, so the sync work. BUT only if you use right click on stereotype in Resource profile and select "Sync Tagged Values and Constraints...".
Do NOT select and drag and drop the stereotype to attribute, is this will be done, duplicates will be still there.

kr
basalt

6
General Board / Re: Problem with "feature" full qualified tagged v
« on: September 10, 2008, 09:06:29 pm »
Hi Dave.
Thx for the reply, i will check also the next build.
I sent a EAP file within the bug report to Sparx to provide a project which points to the problem of FullQualified Tagged Values. So the EAP will only be an example.

kr
george

7
General Board / Re: Problem with "feature" full qualified tagged v
« on: September 10, 2008, 04:13:47 pm »
Hi all.
A new version is out, and I tried to reproduce the problem with the "Problem with "feature" full qualified tagged value" in version 7.1 build 832 an it will be still there, also I reported a bug with a .eap file where Sparx can simple retest it but no reply and no fix still now. So the version 7.1 is still a version which cannot be used by us.

kr
george

8
General Board / Re: Problem with "feature" full qualified tagged v
« on: July 14, 2008, 07:44:59 pm »
Hi «Midnight»
thanks for checking this build too, so I will wait for the next one.

kind regards
basalt

9
General Board / Re: Problem with "feature" full qualified tagged v
« on: July 07, 2008, 06:06:09 pm »
Hi.
I just downloaded and installed build 831 of EA, and the problem with full qualified tagged values will still be there.
So I am not able to upgrade from 7.0 to 7.1

kr
george

10
General Board / Re: Duplicate Tagged Values
« on: July 14, 2008, 07:42:55 pm »
Hi Viliam Durina.
This will be a nice workaround, but I think that Sparx has to provide a builtIn solution for this problem, and so I will wait for the next build of EA to try, but thanks for your solution.

also see: http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1214480695/2#2

kind regards
basalt

11
General Board / Re: Duplicate Tagged Values
« on: April 29, 2008, 07:44:25 pm »
Hi all, I sent a bug report to Sparx and here is the answer:

Code: [Select]
The problem that you are seeing is caused by our introduction of fully
qualified (FQ) tagged values. It is the first part of a bigger plan to
sort out the application of tagged values by stereotypes and get rid of
the synchronize command completely. Until we implement the rest of the
plan, however, the synchronization command needs to be improved.

If an element has the following tagged value before synchronization:

      myTag = "value"

After synchronization, you might have the following tagged values:

      myTag = "value"
      myProfile::myStereotype::myTag = ""

But if you have display of FQ tagged values switched off, this will
appear like this:

      myTag = "value"
      myTag = ""

This is what you are seeing. To switch to display FQ tags, click the
Options button in the Tagged Values window and choose "Show Fully
Qualified Tags".

The correct end result to the above synchronization would be:

      myProfile::myStereotype::myTag = "value"

This is not happening, so we are currently working on a fix.

kr
george

12
General Board / Re: Duplicate Tagged Values
« on: April 24, 2008, 08:23:58 pm »
I found a setting at "Tools->Options->Objects->Show Duplicate Tags". this is unselected as default. I think this setting will ony handle the visibility of tagged values.

thx
george

13
General Board / Re: Duplicate Tagged Values
« on: April 23, 2008, 10:32:11 pm »
Hi Midnight.
Thanks for the reply. I changed the settings by rights click the class object and select "Feature Visibility". I select the checkBox called "Fully Qualified Tags" and tried it again.... The same happened, i got the tagged values twice after sync the stereotype from my profile.

any other ideas?

thx
george

14
General Board / Duplicate Tagged Values
« on: April 23, 2008, 07:18:16 pm »
Hi all,
Since upgrade to 7.1 there is a strange behavior.
There is an attribute with 2 tagged values called "dbColumn" and "isGuiOnly" and both have correct values and a stereotype called "MyAttribute".
Now I mark the attribute in the diagram and open the "Resource/Uml-Profiles" dialog. I will drag the stereotype "MyAttribute" to the selected attribute to sync the stereotype from my own profile. But now i will get 2 additional tagged values called "dbColumn" and "isGuiOnly". So how can i solve the problem or is this a bug in the new version of EA. Also tested in build "829".

thanks
george

15
Thanks AaronB for the fast reply.
I placed a feature request and hope to get it.

Pages: [1] 2