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.
After converting a web service midlet generated by 5.5, all elements in the converted midlet are laid out on top of each other in the visual designer
Tim was faster then me ;) David, I agree that it's more likely bug than enhancement (as you proposed yesterday). this issue is noted in the warning dialog that comes up before the conversion start but who would reads it?
For now this is "as designed". See the notes in the dialog after the conversion. Changing to enhancement and leaving as opened since this issue is hypothetically possible to resolve even through the design uses completely different UI/layout of Flow Design.
Users will :-). Oki - I agree that this is annoying. The issue is that for implementing automatic layout/deserialization would not be simple. I've changed the issue back to defect but target milestone is set to the "future" still.
FlowDesign node locations are recognized and converted. Anyway still the deseerialized locations does not fit to the look&feel of the new Designer. Therefore an user has to press Layout button manually anyway.
That's silly. So throw away the old layout (if it won't fit, what good is it?) and invoke the layout button programmatically.
It is not that easy since the visual library used by Flow Designer requires to have the scene visible on a screen to process the layout. The other problem that we do not have a nice layout algorithm that could be applied - for now I am using simple grid-layout. Because the current conversion is not producing a nice flow layout, I am going to change the converter to remove all flow-data from the converted file. Together with that I will add a loading hook into the flow-designe that in case that there are no serialized flow-data, it should automatically invoke the layout. Reopening the issue.
Fixed in main trunk as described above.
Verified B2