v15ᵦ2 - hangs when closing Special Action window

[MaXyM]

I narrowed it to following scenario:

1. Load a project
2. Select a (database) table from Browser
3. Open Special Action
4. Select General/Tags
5. Close window using [X] button

At step #5 EA hangs every time.

If the window is being closed by Cancel button - it works as expected.

BTW, if I stay on other tab (ie Main), and hit close button, EA asks to save changes, even if I touch nothing. If I answer NO, it still takes some  noticeable time (about 1sec) to close the window. For sure a lot longer than in v14.1

[Geert Bellekens]

Yes, mine hangs as well.

Geert

PS. You can also edit the tagged values from the docked properties window. No need to take the scenery route it that is what you are after.
They are however not found in the tags section, but as a part of the general properties (section table)

[MichaelJ]

Does Sparx EA support read the forums and extract product issues / annoyances / recommendations raised by forum members? Having identified a repeatable bug as described, is it more successful to log directly with the "Raise a Bug" / "Raise a Feature" URL at the bottom of the product's webpage?

[MaXyM]

PS. You can also edit the tagged values from the docked properties window. No need to take the scenery route it that is what you are after.
They are however not found in the tags section, but as a part of the general properties (section table)

Yes I know that.
I found it a bit inconsistent though I already have described it here: https://www.sparxsystems.com/forums/smf/index.php/topic,42779.0.html

[Geert Bellekens]

Does Sparx EA support read the forums and extract product issues / annoyances / recommendations raised by forum members? Having identified a repeatable bug as described, is it more successful to log directly with the "Raise a Bug" / "Raise a Feature" URL at the bottom of the product's webpage?

Some of them are active on the forum, but not in an "official" capacity. They will not create bugs or feature requests based on forum posts.
You should always report bugs via the official channel.
Posting it here merely serves to inform your fellow user.

Geert

[timoc]

Does Sparx EA support read the forums and extract product issues / annoyances / recommendations raised by forum members? Having identified a repeatable bug as described, is it more successful to log directly with the "Raise a Bug" / "Raise a Feature" URL at the bottom of the product's webpage?

Some of them are active on the forum, but not in an "official" capacity. They will not create bugs or feature requests based on forum posts.
You should always report bugs via the official channel.
Posting it here merely serves to inform your fellow user.

Am i right in assuming this is also true for beta releases?

[Geert Bellekens]

Does Sparx EA support read the forums and extract product issues / annoyances / recommendations raised by forum members? Having identified a repeatable bug as described, is it more successful to log directly with the "Raise a Bug" / "Raise a Feature" URL at the bottom of the product's webpage?

Some of them are active on the forum, but not in an "official" capacity. They will not create bugs or feature requests based on forum posts.
You should always report bugs via the official channel.
Posting it here merely serves to inform your fellow user.

Am i right in assuming this is also true for beta releases?

Yes, AFAIK

Geert

[MichaelJ]

Does Sparx EA support read the forums and extract product issues / annoyances / recommendations raised by forum members? Having identified a repeatable bug as described, is it more successful to log directly with the "Raise a Bug" / "Raise a Feature" URL at the bottom of the product's webpage?

Some of them are active on the forum, but not in an "official" capacity. They will not create bugs or feature requests based on forum posts.
You should always report bugs via the official channel.
Posting it here merely serves to inform your fellow user.

Am i right in assuming this is also true for beta releases?

Most Sparx EA users would certainly agree that Support have ready access to a treasure trove of real-world feedback from real-world users talking about their experience of the product. Agree that all bugs should be logged as well as all feature requests. However, if these should be logged, there is no need for a separate "Bugs" or "Features" forums.... 

[qwerty]

Probably this forum should be named "Work arounds for not yet fixed bugs".

q.

[RoyC]

>> Most Sparx EA users would certainly agree that Support have ready access to a treasure trove of real-world feedback from real-world users talking about their experience of the product. Agree that all bugs should be logged as well as all feature requests. However, if these should be logged, there is no need for a separate "Bugs" or "Features" forums....  <<

Quite the opposite. As Geert points out, this is a user forum, for discussions between EA users. When you write about a possible bug in the Bugs and Issues section, you are notifying potentially hundreds of fellow users about the problem you have detected. Some of those users will investigate your problem and tell you either that it is not a bug, or that it is a bug but you can easily do something to avoid it, or that it is a bug and it occurs or does not occur under possibly quite different conditions. Lots of users benefit from the conversation. When you just report the bug to Sparx Support, you don't have that conversation.

The user forum is not the official channel for reporting bugs (or feature requests) to Sparx Support, so what many users do is submit the official bug report with a link to the forum posting. And they post the reply from Support.

[MaXyM]

Probably it would be like you say but:
1. The forum is maintained by Sparx which might be a sign it's support forum rather than community one
2. It's called Sparx System Forum
3. You can find Forum link in Support menu on top of this page - which seems to be strongest argument

On the other side, description of Bugs & Issues subforum says:

Discuss specific usage issues with other users. To report bugs and issues to Sparx Systems, please use the Report a Bug link provided.

Which clears things out definitively.

BTW yesterday I found that official support (menu Support / Contact Us) provides two ways to report an issue:
- bug report (for all users)
- priority bug report (for users with valid support/maintenance licence)

I wonder if "priority" adds anything to a way how fast are issues resolved.

PS. Issue reported in OP still not fixed in beta3

[qwerty]

I don't think so. It probably triggers a check "how many licenses have we sold to that company"; prioritize if it's really a huge number. Just a guess but I'm good in guessing such things ;-)

q.

[MaXyM]

Fixed in v15 beta4 (1503)