From xemacs-m  Sun Mar  9 13:22:09 1997
Received: from beavis.bayserve.net (jmiller@port76.bayserve.net [206.148.244.167])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id NAA10400
	for <xemacs-beta@xemacs.org>; Sun, 9 Mar 1997 13:22:08 -0600 (CST)
Received: (from jmiller@localhost) by beavis.bayserve.net (8.7.5/8.7.3) id OAA10303; Sun, 9 Mar 1997 14:25:40 -0500
Date: Sun, 9 Mar 1997 14:25:40 -0500
Message-Id: <199703091925.OAA10303@beavis.bayserve.net>
From: Jeff Miller <jmiller@bayserve.net>
To: xemacs-beta@xemacs.org
Subject: mine & mouse problems
Reply-to: jmiller@bayserve.net
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII


 I think I remember seeing that mine was ported (mostly) to XEmacs.  Fired
 it up & it looks pretty cool with the pixmaps. [thanks Jen!]

 But, my mouse seems to do nothing.  button1 doesn't do anythig & button3
 brings up a typical XEmacs button3 menu [i.,e copy/paste/undo ...]

 From the mine code & help text, it seems like these buttons should be
 bound to mine funtions.

 If I do a C-h k button1   I get this in the mini buffer
Wrong type argument: number-or-marker-p, nil

& this backtrace in a buffer

  # bind (standard-output stack-trace-on-signal debug-on-signal stack-trace-on-error debug-on-error point)
  mine-point-to-x\.y(nil)
  # bind (point)
  mine-goto-point(nil)
  # bind (event)
  mine-mouse-hit(#<buttonup-event button1up>)
  # bind (command-debug-status)
  call-interactively(mine-mouse-hit)
  # (condition-case ... . error)
  # (catch top-level ...)

Things work ok if I just use the arrow keys along with space & return.

