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.
To get cleaner code (yet not necessarily memory efficient) I've sometimes turned off lazy initialisation on "everything" to see the program logic better. If I do that the simulator simply can't run the application. Is this at all supposed to work based on the way that pre-init, post-init is auto-generated when using VMD? Not a major issue though. Where I've used lazy initialization turned off successfully is for e.g. alerts that I place on the VMD diagram but don't connect to anything, as the intention is to control display via my software (e.g. debug alerts etc). In that case it saves on coding to have them pre-initalized.
I can confirm that. Here a fragment of code which causes the problem: helloStringItem = new StringItem("Hello", "Hello, World!"); helloForm = new Form(null, new Item[] {helloStringItem}); helloForm.addCommand(exitCommand); helloForm.setCommandListener(this); exitCommand = new Command("Exit", Command.EXIT, 1); exit command added before created.
Anders Borg wrote: > Seems to fit the bill. > > I also wanted a global off switch for lazy initialization, but if it doesn't > work as intended (at all) then that would be no point asking for. > > I use lazy on everything now, which is not a problem. Doesn't matter that > much except the code gets a bit bigger (yet data hopefully becomes smaller). > > All pre/post-init/action code I make as method calls to code elsewhere. That > way I don't have to see that much of the auto-generated code. The stability > of the code generation from VMD diagrams seems to be very high overall.
the generated code is wrong -> increasing priority to P2
The problem is in topological sort while resolving non-lazy-initialized components. Fixed in main trunk.
reopening, I'm unable to don't use the lazy initialization in HelloMidlet. Unselect Lazy intitialize on the helloForm and switch to Source. there is a warning that it forced the lazy initialization on again.
Fixed in trunk
Lazy initialised doesn't work for wait screen, when WS success or failed transition is going to directly the same WS, it force me to use LI. TYPO in the warning Dialog.
Fixed in trunk. Self-references are removed from dependency map. Typo is fixed too.
verified with branch build 200604180200
v
close old issues