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.
jdk 1.5.0 b35 - only this build 32c is ok -Invoke "Mount local FS" - the wizard does nothing - you cannot change disc, directory, etc.
FileChooser demo works fine.
There was a bug in the old JFileChooser - if you called setEnabled(false) on it, its subcomponents were still enabled. We have a workaround in PropertyPanel (see CustomEditorDisplayer.setEnabled()) - it was there for a long time, I just copied it from the old PropertyPanel. When you setEnabled/disabled on a PropertyPanel in custom editor mode, it will walk the component tree and enable or disable everything. In fact, on 1.4.2, even after the file tree is disabled you can still navigate it and create new folders if you double click :-/ I wonder if they "fixed" this behavior a little too agressively. Please be absolutely sure that the current trunk build works on 32c - I did one change that affects enablement (but only if a client property is set) today, so we should be sure that my fix didn't affect it. We can put some logging in FileEditor and see who disables what when. There are also a lot of filechooser enhancements we've requested from the JDK team. If they're starting to integrate these, it wouldn't surprise me if JFileChooser were unstable for a few builds. Where can I find a change log?
Reproducible on linux as well. Tim, I will send you more info. What build of IDE contains your mentioned fix of enablement?
Today's build should have it - I did it yesterday afternoon so the editor module could resolve its Inherit checkbox enabled for default color/etc. bug. What it does: if a component in a custom editor inside a PropertyPanel returns Boolean.TRUE from getClientProperty("dontEnableMe"), the PropertyPanel will not try to change its enabled state. I can't imagine how it really affects the mount wizard (since I don't see the problem on 1.4.2) - it would be a big coincidence if there already is some "dontEnableMe" client property. I just mentioned it to be sure there were no surprises.
Sorry for bothering again Tim, I was looking thru our not-yet-evaluated bugs and found out that you own ten of them. As release 3.6 criteria is to have all of them evaluated (as well as to not have any P1, P2), could you please look at these bugs and set the target milestone to something else than TBD? Thanks in advance and one again, sorry for bothering.
This is a JDK bug which was introduced recently. If you set a JFileChooser as follows: jfc.setFileSelectionMode(jfc.DIRECTORIES_ONLY); jfc.setMultiSelectionEnabled(true); it will not be possible to change the working directory. We need to file a high-priority Swing bug. Lukasi, I'm working from home, off SWAN today - either I can file it tomorrow, or you can today (and cc me). I will attach a simple test case.
Created attachment 13504 [details] A very simple test case that reproduces the problem
Addendum: If you comment out setMultiSelectionEnabled() (I just did so my test builds are usable while I fix other bugs), you can change the directory in the combo exactly *once*. After that it ignores all changes.
I have filed a P1 bug against JDK 1.5, number 4997128. Hopefully it will be attended to in short order.
ok, verified. I'm sorry, Tim, I've missed it yesterday :(
*** Issue 40444 has been marked as a duplicate of this issue. ***