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.
Summary: | property sheets behaving oddly when run outside the IDE | ||
---|---|---|---|
Product: | platform | Reporter: | jarecsni <jarecsni> |
Component: | Explorer | Assignee: | _ tboudreau <tboudreau> |
Status: | CLOSED INVALID | ||
Severity: | blocker | CC: | jglick |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 26086, 29447 | ||
Bug Blocks: |
Description
jarecsni
2002-07-25 13:41:28 UTC
*** Issue 26014 has been marked as a duplicate of this issue. *** *** Issue 26014 has been marked as a duplicate of this issue. *** *** Issue 26014 has been marked as a duplicate of this issue. *** *** Issue 26015 has been marked as a duplicate of this issue. *** A problem is in NodeTableModel class, there is a code is referenes out of explorer.jar and out of the dependent jars. This code have to be handled safer. I create new task 26086 blocks this issue. IMHO this is INVALID - you cannot have core.jar in the classpath without also openide-remainder.jar, which would include the dialog classes. I agree with Jesse, the core property editors expect to work with the rest of netbeans' infrastructure. If it's not there, things can break randomly. It might not be a bad idea to find a way to split out the some of the core property editors as its own binary lib - ones for common classes like String and Double. Or move the editors for more basic classes like these into openide. I imagine at least the propertysheet portion of the explorer library is not so useful without some of them, if people are putting core.jar on their classpath just to have access to them. verified, closed Well, what actually happened here? AFAICT if DialogDisplayer.getDefault() does something vaguely reasonable (i.e. pop an unparented JDialog, or one parented to Frame.getFrames()[0]) without the presence of an implementation, property editors should more or less work. Splitting the core property editors between editors for JDK classes and NetBeans classes is probably a necessary prerequisite to using core on the classpath in a standalone app and not having at least some pathological behavior, but I'm not completely convinced this should have been closed. |