Christopher Masi's email of 27 Jan 2004
Thanks for taking the time to send such detailed feedback.
> I downloaded the JmolApplet 10pre5 release the
other day, and started
> learning how to embed it into my pages. I noticed
some odd behavior
> while I was experimenting with the applet.
> If a user "command clicks" to activate the
contexual menu and then
> changes his mind and wishes to dismiss the menu, the
user must click
> inside the JmolApplet window. If the user clicks
outside the JmolApplet
> window, the contextual menu will not be deactivated.
Hmmm ... good catch. There are probably a few more
that we need to track.
Not sure how to handle it ... maybe we need to watch
the cursor position
and reset our state if the cursor goes outside our window.
> Admittedly, it took me only two clicks to realize
that I might want
> to try clicking inside the JmolApplet window, but I
wonder if others
> might become frustrated and simply close the entire
> Actually, I just managed to bring up a contextual
menu that nearly
> covered the entire JmolApplet window, only one column
> remained. I observed this behavior in Mozillia 1.6
and Safari 1.0.1
> running on OS X 10.2.8. Strangely, one does not have
to click in the
> JmolApplet window to dismiss the contextual menu when
> embedded applet using Camino 0.7 (of course, as you
> mousing doesn't work correctly in Camino)
Interesting. I'll bet the behavior could be very
browser and os platform
dependent. The different OSes could generate different
events and the
different browsers may or may not pass those events to
Could be a 'challenge'.
> Another contextual menu issue that I noticed was
that in Mozilla and
> Camino the full contextual menu doesn't appear on
screen. Mozilla puts
> the contextual menu just below the mouse click, but
some of the menu
> winds up off the screen. With Camino, the position of
> menu depends on whether the Toolbar is showing, When
the toolbar is
> showing the contextual menu appears several
millimeters below the
> initial mouse click. When the toolbar isn't showing,
> menu appears just below the initial mouse click. 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?
If so, I honestly don't know if there is anything I can
do about it.
> In contrast, Safari will move
> the contextual window up, so the whole menu fits on
> Another weird one that happens in Mozilla. Once
the mouse is used to
> rotate a molecule, my keyboard no longer works. For
> "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.
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.
Which JVM is Mozilla using? If it is using 1.3 then
I'll bet it is an
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.
> This isn't a problem in Safari.
> These issues seem more like browser issues, but I
just wanted to make
> certain they weren't JmolApplet issues.
There certainly are some 'browser issues' involved, but
I suspect we can
make some changes/enhancements to the JmolApplet to
better handle the
Log in to post a comment.