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.
[WINXP][20051016] evalute this: 1) Create new suite 2) create new module in this suite 3) in module,create by wizard TC "aaa", check "open at startup" 4) in suite customizer, choose "Create standalone application" radiobutton 5) run suite 6) platform is launched, window does not open. 7) If you open it from Menu, you get output: [WinSys.PersistenceManager.getTopComponentForID] Problem when deserializing TopComponent for tcID:'aaaTopComponent'. Reason: Top component aaaTopComponent could not be located or loaded from Components folder. Cannot find aaa component. This works ok if: module is not in suite, but standalone
i've tried to reproduce step by step with current trunk (on macosx) and it works just fine for me. please include more details.
Still reproducible. And the reason is that i place the window to *output* position. Then if suite is set to standalone application, some clusters are excluded, and there is *no more output position present* in bare platform. In general, there should be at least some kind of warning dialog when you are changing in suite clusters and module settings - something like "Dear user, you decided to uncheck ...., this might affect functionality of this and that, do you want to proceed?? YES/NO"
too bad. I admit the current design of modes is sub-optimal, having all defined in one place in the platform would be ideal for multiple reasons. but it's not the case. <rant> But as I mentioned in multiple reports previously, we're not in the RAD business, our wizards are plain code generators and we cannot maintain the code constistency over time and space. </rant> I suggest to close as INVALID or WONTFIX. up to you though, jesse.
Agreed. If you run a wizard when the module is one basic configuration - an IDE module - and it generates code which will only work when installed in the IDE, and you then run the module against the bare platform, it will not work. We cannot retroactively fix your code.
I'm OK with "code genarating wizards", but reconsider again using some kind of warning dialog as suggested.. all parts of API support seem to me "naive-user proof", why this not?? Mariane, your opinion as "QA master":)??
The IDE cannot know what edits you might have made to a generated wizard after you made it. The code you have is not under apisupport's control after you make it.
ok, closing.