> I *cannot* reproduce the problem
> * on Windows 2000, Java 1.5.0_03,

I have the same except my Java is 1.5.0_01, but I don't think this is the
issue

> * by dragging C:\Program
> Files\XMLmind_XML_Editor\doc\user\userguide.xhtml into XXE,

It doesn't matter how the file was opened.

> * by using GNU Emacs to modify  C:\Program
> Files\XMLmind_XML_Editor\doc\user\userguide.xhtml,
> * with the binding[*] below:

It doesn't matter which application, the Notepad.exe can be used too (of
course the newlines doesn't work in notepad well)

>
> ---
>   <binding>
>     <keyPressed code="F3" />
>     <command name="XXE.open" parameter="[reopenIfNewer]" />
>   </binding>

I use menu to initiate Refresh:

<menu label="XHTML" mnemonic="X">
<item label="Refresh from file"
command="refreshFromSource">
</item>
<separator />
<!-- old XHTML menu will be inserted here -->
<insert />
</menu>

> * May be you have bound command refreshFromSource to a keystroke that
> cannot work properly (Esc, Alt-something, etc). Explanation depends on
> the keystroke you have chosen.

No, see up.

> * May be the external application you use to modify your document locks
> the file.

No, see up.

> * May be XXE ``crashes''. With Java, ``crashes'' are very soft. They are
> almost never fatal. You need to run XXE with a console and send us the
> error messages possibly displayed in this console.

I tried to run XXE with console (modifying xxe.bat to use java instead of
javaw), but I saw no output. Should I set something so I see debug traces
even if everything works fine?

Some more observations (clarifications): When I externally modify the file
and XXE contains unsaved data and I do Refresh, XXE asks "...discard changes
and reload.." and everything works fine. But when file in XXE is saved and I
reload modified file (it's enough the set the date on file), XXE says
nothing (that's fine I suppose), but the cursor stops blinking and I cannot
edit (but I can place cursor on another location). When I refresh again,
everything works fine.

Fortunately this is really minor problem, the second refresh cures the edit
"lock".

Jan




Reply via email to