This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 190705 - VMD becoming unresponsive
Summary: VMD becoming unresponsive
Status: NEW
Alias: None
Product: javame
Classification: Unclassified
Component: Visual Designer (show other bugs)
Version: 6.x
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Roman Svitanic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-01 12:59 UTC by albus
Modified: 2013-04-09 11:23 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
How my Flow View currently looks like (213.51 KB, image/png)
2010-10-01 13:14 UTC, albus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description albus 2010-10-01 12:59:24 UTC
I am using some considerable amount of GUI objects, and the VMD hogs a lot on some PARTICULAR operations.

In Flow View:
1. When moving elements out of the available space
2. When fiddling with the flow arrows, i.e. adding new ones, etc.
3. Most annoying: when going OVER arrows that are on the edges of the screen. When one moves over them, they get somewhat "bolder" and NetBeans is completely unresponsive.

Both in Flow and Screen Views:
4. When invoking the context menu for an element in order to open the options screen.

In all those cases the "Palette" and "Properties" windows have been closed in order NOT to interfere.

If I have them on, I am experiencing one more issue: when changing from Code to Screen/Flow View (and vice versa) one has to wait a lot. This doesn't happen, if the "Palette" and "Properties" windows are closed. The obvious problem for the Flow View is that it is always shown without the Palette/Properties window first, and when then the palette window is opened, the Flow View has to be redrawn.

I'll upload some vids/pics to show you.
Comment 1 albus 2010-10-01 13:14:16 UTC
Created attachment 102222 [details]
How my Flow View currently looks like
Comment 2 albus 2010-10-01 13:21:00 UTC
Here are some videos on issues #3 and #4.

Issue #3

You see WHY it's annoying: I've got to use the mouse very carefully so that not to go over an arrow that incidentally might be on the edge of the screen.

http://www.youtube.com/watch?v=FuL5dggA-0M

Issue #4

It turns out, that there is no problem in invoking the context menu for COMMANDS and such items. The problems is with Forms, Methods, etc. Also, if the menu has been invoked once, invoking it again on the same item doesn't take time.

http://www.youtube.com/watch?v=ZLZizLMcg08

Thanks, guys!
Comment 3 albus 2010-10-02 12:19:25 UTC
Turns out that both issues #3 and #4 are due to the arrows resizing the canvas by A FEW pixels. I mean, when I invoke the context menu on any object that has in-out arrows, all arrows that are going in and out get selected and therefore need a few pixels more around themselves (the usual behaviour).

Can you just make the canvas size be always big enough so that the arrows can fit even when they are selected!

Thanks!

P.S. sorry if I sound unclear, If necessary, I can explain it again.
Comment 4 David Strupl 2013-04-09 11:23:00 UTC
Assigning to the new owner of javame modules.