briel@sctc.com (Marc Briel ) (12/27/90)
I am having a few annoying problems with Mac X and would appreciate any helpful hints available. I am running MacX 1.0.1 with MacTCP on a Mac II connected to appletalk. Appletalk is connected via a Kinetics Fastpath gateway to a Sun fileserver on Ethernet. 1. Remote commands don't always work. Remote commands to start an xterm on the Mac display are sometimes not received by the Sun fileserver. No command output is generated. However, NCSA Telnet can be used to login to the fileserver and an client xterm window can be started successfully via a direct command to the login shell on the Sun. This behaviour appears at random (apparently), persists for days, and again disappears at random leaving Remote commands functional again. 2. Mouse commands appear to be ignored sometimes. Some of the "x-mouse" commands in Emacs do not function occassionally. It appears that the commands are not received by the application on the fileserver. If you repeat the mouse operation one or more times, it eventually takes. Some other mouse commands in Emacs do not work reliably unless the current cursor is preset (left-click) to the start of the region to be dragged. 3. Some realtime mouse interactive applications don't work properly. Screen updates appear to always take precidence over mouse events resulting in a large time lag between mouse operations and visable effects on the screen. For some applications (such as XTrek) the lag is severe enough to make the application unusable. The behaviour also indicates that mouse position updates are not always sent with mouse button events causing the application to act on the button events using stale position information. 4. Window manager annoyances a. The active window for the mouse and the screen are sometimes inconsistent. When the mouse is clicked to change the active window, the display is updated as expacted but mouse events are sent to the previously active window. This can be cleared by converting the previous window to an icon and then back. b. The screen cursor is sometimes updated locally before the event is sent to the client application on the fileserver. As a result, mouse commands sometime operate on "stale" cursor position (with respect to the users perception. There are numerous other glitches but these have been the moat annoying and recurrent so far. Any info is appreciated. Thanks, Marc Briel briel@sctc.com P.S. Any new info on MacX compatible, 3-button mice? I say a 3-button trackball but it would requires two hands to use it in an X enviroment (i.e. one for the buttons, one for the ball).
Marc.Briel@f20.n226.z1.FIDONET.ORG (Marc Briel) (12/27/90)
Reply-To: briel@sctc.com
I am having a few annoying problems with Mac X and would appreciate
any helpful hints available. I am running MacX 1.0.1 with MacTCP on a Mac II
connected to appletalk. Appletalk is connected via a Kinetics Fastpath
gateway to a Sun fileserver on Ethernet.
1. Remote commands don't always work.
Remote commands to start an xterm on the Mac display are sometimes not
received by the Sun fileserver. No command output is generated.
However, NCSA Telnet can be used to login to the fileserver and an
client xterm window can be started successfully via a direct command
to the login shell on the Sun. This behaviour appears at random
(apparently), persists for days, and again disappears at random
leaving Remote commands functional again.
2. Mouse commands appear to be ignored sometimes.
Some of the "x-mouse" commands in Emacs do not function occassionally.
It appears that the commands are not received by the application on
the fileserver. If you repeat the mouse operation one or more times,
it eventually takes. Some other mouse commands in Emacs do not work
reliably unless the current cursor is preset (left-click) to the
start of the region to be dragged.
3. Some realtime mouse interactive applications don't work properly.
Screen updates appear to always take precidence over mouse events
resulting in a large time lag between mouse operations and visable
effects on the screen. For some applications (such as XTrek) the lag
is severe enough to make the application unusable. The behaviour also
indicates that mouse position updates are not always sent with mouse
button events causing the application to act on the button events
using stale position information.
4. Window manager annoyances
a. The active window for the mouse and the screen are sometimes
inconsistent. When the mouse is clicked to change the active window,
the display is updated as expacted but mouse events are sent to the
previously active window. This can be cleared by converting the
previous window to an icon and then back.
b. The screen cursor is sometimes updated locally before the event
is sent to the client application on the fileserver. As a result,
mouse commands sometime operate on "stale" cursor position (with
respect to the users perception.
There are numerous other glitches but these have been the moat
annoying and recurrent so far. Any info is appreciated.
Thanks,
Marc Briel
briel@sctc.com
P.S. Any new info on MacX compatible, 3-button mice? I say a 3-button
trackball but it would requires two hands to use it in an X enviroment
(i.e. one for the buttons, one for the ball).
+ Organization: Secure Computing Technology Corporation
--
Marc Briel - via FidoNet node 1:105/14
UUCP: ...!{uunet!glacier, ..reed.bitnet}!busker!226!20!Marc.Briel
INTERNET: Marc.Briel@f20.n226.z1.FIDONET.ORG