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.
In the case of form editor, the responsiveness of appearing the inspector, palette and properties is unpleasantly slow. This should be analyzed; if it shows up it is caused by slow layout/painting of the components, then it should be fixed in form editor (e.g. together with redesigning the palette, see issue 36125).
Component Pallete is the most problematic component. Has to be imporved much. Assingning there.
I don't say the palette is not problematic, but I'd like to see some performance analysis as a proof that the main problems are there and not in the infrastructure - before reassigning to form editor. I may do some measuring and profiling if needed. Also there are other questions, like e.g. if we should not ensure generally that the window group is opened synchronously with the triggering component so all components appear just at once in the final, not additionally as it is now. (IMO this was strong HIE request on group implementation.)
I expected you will do the analysis, I have a lot of other work to do. It is asynch now. But will be synch if the issue #36679 becomes fixed. Anyway the asynch is not that problem... earlier we were investigating it a bit (no concrete resulte were put down), therefore I point you directly to that component.
Okay.
Why do you think this issue depends on issue #36679. It doesn't.
I think it is related - if the whole window group is opened synchronously with the triggering component (not some time after), the user experience is better. It is UI responsiveness issue. You are right if talking just about rough performance of the window group opening - that's independent problem.
Looks much better now when issue 36679 is fixed. Close this if you want, or make it a duplicate of issue 36949.
Resolving as duplicate *** This issue has been marked as a duplicate of 36949 ***