v15(beta 1502) - Systems hangs when context menu open

[MichaelJ]

Hi everyone,

Would like to confirm whether or not anyone experiences the same system bug with the latest installation of Enterprise Architect (1502) which exhibits the following behavior: (have logged this issue with support, via the 'Report a Bug' function, and provided detailed step-by-step instructions and screenshots as well as process-analysis using SysInternals tool, and the impression I have right now, is there's a lack of willingness to admit this is an ACTUAL bug to be dealt with; if other other users experience the issue, please would inform support too so they're made aware of the seriousness of this bug)

Steps:

1. Create a new project
2. Create a new default model
3. Create a new UML diagram (any)
4. Drop a class element from tool box onto the drawing canvas
5. Select the element and open the properties dialog of selected element
6. In the element properties window, navigate to "Tags" sheet on the right side
7. Right click anywhere in free space of the toolbar that houses the row of icons
8. Don't do anything; wait around 30 seconds for Windows to show the usual 'System Hang' ghosted effect

Image:
(would like to insert an image to show, how does one do so on the forum?)

Analysis:
Initial analysis shows that the context menu displayed in this properties dialog does NOT disappear when it loses focus, which ultimately causes the system to hang. The same context menu correctly disappears in other parts of the product when it loses focus, for example in the 'Find Package' text box located at top-right.

[qwerty]

You may have noticed the "beta" in V15. So you can't expect any bug confirmation.

If you want to show pictures here you need to upload them to any public server and use the link. Welcome to the 21st century :-/

q.

[MichaelJ]

You may have noticed the "beta" in V15. So you can't expect any bug confirmation.

Thanks for the response. Yes, am aware that it's a 'beta', however the question is raised for two reasons:

1) this bug has been logged with support, with video, pictures, and program thread analysis to help Sparx resolve this issue and the impression from support is that "it's not a bug", "can't replicate after one click" or "works on my PC!" syndrome. Brand new installation of product, and bug can be reproduced time-after-time.

2) the issue is raised for other users to confirm they encounter the same. Surely the more users that log this blatant bug, the sooner Sparx can prioritise to fix it in the next release.

[qwerty]

Well, that's a good intention and it should be done this way. Just know that I'm that Jack-in-the-box that pops up whenever someone tries to report a bug an hopes for a soon fix. Wonders happen. But they are still wonders then. Good luck anyway ;-)

q.

[Geert Bellekens]

I can confirm that it happened on my machine as well.

Geert

[MichaelJ]

Well, that's a good intention and it should be done this way. Just know that I'm that Jack-in-the-box that pops up whenever someone tries to report a bug an hopes for a soon fix. Wonders happen. But they are still wonders then. Good luck anyway ;-)

q.

Hi qwerty,

Good news.

The bug logged concerning this issue has been dealt with and resolved in build 1503! (provided as much detailed information as I possibly could, even including internal thread timings to help identify the location causing this bug).

Am really glad the Sparx support team paid attention and dealt with the issue, since it raises confidence that the product is getting better, even perhaps on its way to becoming the best tool on the market (if (stale/aged/stagnant) management will pay heed to user forum bugs / features, especially to 'Bug/Feature' requests ordinary users take time to provide)

[qwerty]

Still happy to hear those stories! I'm still a bit underwhelmed from what happened in the past few years compared to that furious start I had with Sparx in the early 2000th.

q.