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.
From time to time (and actually it's pretty often in my case) all the elements in Flow View (e.g. Alerts, Forms, Entry Points, etc.) get absolutely disordered. That is, they are crumpled in the upper left corner, one on top of the other. It's pretty messy, and is tiresome to have to fix elements' positions when developing applications that rely pretty much on the Flow View (as it is a great tool for fast development).
After some testing I found that the following situations DO NOT reproduce the bug: 1. Forcibly closing NetBeans 2. Forcibly closing NetBeans while the Flow Window is Open 3. Forcibly closing NetBeans while the Flow Window is Open and I have made changes to the diagram without saving them As I said, NONE of these reproduced the bug. By "forcibly closing" I mean shutting the app through the TaskManager (I also shut all instances of java.exe and javaw.exe for good measure).
Please try to find some reproducible case or at least a hint. It never happened to me.
I am really, REALLY sorry that I hadn't helped. It happened to me yet again (and for no apparent reason). I'll do my best to reproduce it and give info. Thanks for the support.
Created attachment 102074 [details] NetBeans's message log
Created attachment 102075 [details] What NetBeans looks like after the occurrence of the bug
Happened yet again. One can see for themselves now. The log says there is something wrong happening. One more thing: I didn't do anything wrong. Closed NetBeans and after a few hours opened it up again. And: tada. Some little nasty bug waiting for me :-D. I'd be very grateful, if one could fix it. It's incredibly annoying having to fix it manually. And principally moving objects around the VMD is really slow (especially when there are some good amount of them (lets say ~12-15 screens)). Why doesn't one try make the VMD editor a bit more responsive (the performance is really slow sometimes). Thanks a lot, everyone!
Something else: is there a way to backup the VMD's data manually from time to time? I mean the position of the objects on the window canvas.
And more: I decided to use the automatic layouting feature. It helped a bit. But after that I closed NetBeans. It didn't say there were any changes to save (I thought NetBeans manages the VMD in some other way) so I didn't find it strange. However, when I reopened NetBeans, it turned out that it hadn't saved the layout after all. So I need to make some change to the code, so that the layout could be saved. In other words, the `Layout` action didn't trigger any saving response from NetBeans. After layouting, one must be either able to save the changes manually or should NetBeans take care of it. I think that's another bug, too, right? Thanks!
David, do you have any idea why this randomly happen in VMD?
I think, I've found out when the bug occurs. I am using GIT to manage my project, and from time to time I need to "go back in time", i.e. reverse some changes, etc. Well. Yesterday I did that and everything is mixed up again. Guess what. It took me ~40 mins to "automatically rearrange" the VMD elements. Not to mention that it's taking around 20 to open the flow view even though the elements are nicely (at least visually) arranged now. My guess is that there is some cache info for the VMD that is OUTSIDE the app folder, and when I restore some previous release of the code, Netbeans gets (very) confused. Just thought you'd better know. I'd be happy if anyone would take this seriously. Of course, j2me is no longer a serious concern, as most of the attention is at Android, but still... Thanks guys!
This happened to me also once. I think it is GIT and cache related. Could it be that the VMD file is cached also? @albus: Maybe change to FreeRouter which is a much faster for reflow :) http://www.cwision.de/projects/NetbeansFreeRouter/
Krisha, I think it's cache related, too, but didn't have the time to investigate any further. You should have said about the FreeRouter a week ago, when I spent three days rearranging my flow for I needed to change some paths and add some new elements. You see, it took ~30 minutes a click :-) Now, I have to say, I am deeply thankful for you suggestion. It's still slow, but it takes ~17 seconds to show up, which compared to 30 minutes, i.e. 1800 seconds, is 105x boost :-D And it takes no time when I click on a displayable :-) Thanks a lot! I owe you one!
Assigning to the new owner of javame modules.
Marking as WORKSFORME, not able to reproduce it and moreover issue is long time without any update.