Re: [Jmol-users] JmolApplet releasing 'mouse down' is unintuitive and other observations

[Miguel H. <mt...@mt...>]

Chris,

>>> In both cases, part  of
>>> the contextual menu is off the screen.
>>
>> You are saying that it is 'off the screen'. Do you mean that you are
>> clicking near the edge of the screen and then the menu spills off the
>> edge
>> (or bottom) of the screen?
>
> Yes, exactly. Safari seems to be "smart enough" to move the contextual
> menu up a bit so it doesn't spill off the screen, Camino and Mozilla
> allow the menu to spill of screen. Camino has the extra oddity that the
> position of the menu also depends on whether the button bar is hidden
> or showing.
>
>> If so, I honestly don't know if there is anything I can do about it.
>
> I guess I can send a bug report to the Mozilla and Camino developers?

Yes, I think you should file a bug with with the Mozilla and Camino teams.

On Linux the JPopupMenu is repositioned so that it remains on the screen.

>>> In contrast, Safari will move
>>> the contextual window up, so the whole menu fits on the screen.
>> That's good.

It is conceivable that the Mozilla/Camino folks will say that it is a Java
issue ... and perhaps it is. But then, why does it work OK on Safari?

What version of the JVM does Mozilla/Camino use? If it is using the 1.3.1
JVM then maybe it was a Java bug that has been fixed. In which case, the
Mozilla/Camino folks should confirm that the behavior is OK with 1.4.1.


>>> Another weird one that happens in Mozilla. Once the mouse is used
>>> to
>>> rotate a molecule, my keyboard no longer works. For example, the
>>> "command w" key combination doesn't work, and I cannot type in the
>>> url field. Clicking the close button works, and the "command q" key
>>> combination works too.
>>
>> Here is my theory. Once you click on the JmolApplet it has focus.
>> Keyboard
>> events are then sent to the JmolApplet.
>
> That sounds like a good theory. More information: when a Jmol window
> that is inside a Safari window is clicked, command key (command w,
> command m, etc) combinations are sent to Safari, but regular keys are
> not sent (no "tabbing" to the url field).

Jmol does not currently* handle/consume any keyboard events. Therefore all
keyboard events should be propogated to the containing window ... in this
case Safari.

(* I say 'currently' because it probably will do so in the future).

... 1 minute later ...

I just tried this out on Mozilla+Linux and the behavior is different. It
must be the case that they are not propogating the keyboard events to the
containing browser.

So, who knows?! It looks like the handling of keystrokes must be very
browser-dependent.

It is interesting that Safari appears to treat command keys differently
from normal keys.


> Clicking anywhere in the
> Safari window returns the keystrokes to Safari (tabbing to the url
> field works). Incidentally, the Java applet ChemSample (its home page
> has disappeared from the internet)
>
> http://www.wsc.ma.edu/cmasi/organic2/diels-alder/diels.html
>
> has the same problem when used with Mozilla 1.6. I should also note
> that following a link to another page or reloading the same page will
> give keyboard focus back to the browser window.

In summary ... keystroke handling seems to be browser-dependent ... so we
are not going to worry about it.


> As far as I can tell,
> both Mozilla and Safari rely on Apple's Java Plug-in to run Java Applets

Correct, but they may be using different versions of the Java Plug-in.

>> The JmolApplet ignores keyboard events. Since they are not handled
>> then they should be propogated to the enclosing window ... Mozilla.
>> Seems  like
>> this isn't happening.

Hmmm ... looks like I am repeating myself :-)

>> Which JVM is Mozilla using? If it is using 1.3 then I'll bet it is an
>> Apple bug.
>
>> You can determine which JVM is being used by opening Tools -> Web
>> Development -> Java Console and then looking at the first few lines
>> after
>> the JmolApplet is loaded.
>
> Unfortunately, the Java Console choice is grayed out in that menu. I
> don't know why. I poked around a bit and checked the versions of the
> Java plug-ins and the are v 1.3.1. Apple's web site says the following
> about their 1.4.1 update:
>
> The Java 1.4.1 Update 1 adds the following enhancements :
> Improved Java applet support for Safari and other web browsers that
> support the Java Internet Plug-In.
> Improved drawing correctness and performance.
> This update includes Java 1.3.1.
>
> I think Mozilla uses the Apple Plug-in, because removing the plug-in
> from the system level Library disables Mozilla's ability to run Java
> applets.

My cursory understanding is that Apple left the JVM 1.3.1 installed.
Applications can choose which JVM they want to use. If there is not a
specific Mozilla release that upgrades it to 1.4.1 then it will continue
to use 1.3.1


> Thank me, that is funny.

I appreciate your taking the time to investigate the problems and report
on them so clearly.


Miguel