Tom Malaher wrote: > A trio of issues: > > 1) The search dialog. When it pops up, can you force the focus to the > "Search" field? > > 2) Searching: When I search for a "?" character (not in regexp mode), > the search stops at the first "empty" element it finds (the grey > rectancles). And the "find next" command will not make the search > move to the next spot. I have to manually move the insertion point > past the placeholder. If an actual "?" is found, the search behaves > properly. > > 3) Interesting failure: this one may be hard to explain or duplicate, > but just in case it helps to track something down: > I was editing a document, and had just saved it (using ctrl-S I > *think*). I left the document alone for a few minutes, then made one > minor change and saved again (but this time I used Alt-F/S, which > leaves an "F" character at the insertion point [see previous > correspondence]). I ended up with a "Null Pointer Exception" dialog, > which I dismissed. When I checked the file on disk it was zero > length (so the save had failed). Luckily the backup file had all but > my last change in it. Now, I can't exactly remember what state XXE > was actually in after I dismissed the NullPointerException dialog (or > even if it was still running.) So if this report isn't useful, > never mind. I'll watch out more carefully for this behavior in the > future, and record the information from the NullPointer dialog.
Point (1) and (2) are solved in the product (where there is no search/replace dialog but a non-modal search/replace tab in a tabbed pane.) (I'll nevertheless fix (1) in the M1.3p3). Point (3) is really strange: I have never ever seen a dialog with just a "Null Pointer Exception". On Windows (like 99.9% of people, you work on Windows, don't you?), exceptions are generally unnoticed, except if XXE freezes. What you have described can easily be reproduced on a Unix/Linux system (I'll add this one to the FAQ.): 1) If you use Java 1.4. 2) If your home directory is located on a disk mounted by NFS. 3) The NFS server does not support file locking (example: some Linux NFS servers). In such case, *any Java application* reports a warning each minute or so and ends up running out of file handles which causes *exactly* the kind of error you described. Please, try to duplicate this one and please, do not forget to mention which version of Java and which operating system you are using. And, hum, hum, hum ;-), the correct place to report bugs is: xmleditor-support at xmlmind.com (you don't have to subscribe to this mailing list just to report bugs).
