T.R | Title | User | Personal Name | Date | Lines |
---|
118.1 | More likely a software problem... | LDP::WEAVER | Laboratory Data Products | Wed Jun 08 1988 21:24 | 10 |
| Sounds like a problem with the keyboard processor (6301), but
I doubt it. More likely you have installed some software that
is causing the problem; did it happen after you started using a
particular piece of software? Does the desktop exhibit the problem?
Try powering down your machine, then power it up without any disks
attached/inserted, wait for it to timeout to the desktop and see
if the problem still persists. If the problem remains after all
this, then it is probably the 6301.
-Dave
|
118.2 | | RAINBO::COUTU | He who will not risk, cannot win. | Thu Jun 09 1988 13:23 | 4 |
| Okay, sounds like a good suggestion. I'll give it a try tonight
and see what happens.
Dan
|
118.3 | One possibility | PRNSYS::LOMICKAJ | Jeff Lomicka | Thu Jun 09 1988 14:26 | 22 |
| Whack (or any of my other applications) could be at fault here.
When using GEM, you are allowed to request left button events, right
button events, or events that have both buttons pressed. You may NOT
request "either left button or right button" as an operating mode,
which is, of course, the only mode I'd ever want to use. (Stuuupid,
stupid, stupid. I'd like to ring the neck of a DRI engineer for this
one.) In order to get reasonable access to the left button, that is,
left button OR right button instead of left button AND right button,
Whack splices into the interrupt vector for mouse handling, and
converts all right button events into left button events, and keeps
it's own event queue. GEM is then happy to report right button events
for all mouse events, and I look in my own queue to see what really
happened.
As a side effect, any desk accessory you are running with Whack will not
be able to access the right button.
The interrupt vector is put back when Whack exits, so it SHOULD return to
normal. Note that if Whack bombs instead fo exits, it will leave this
code behind.
|
118.4 | Eureka! | RAINBO::COUTU | He who will not risk, cannot win. | Thu Jun 09 1988 18:52 | 12 |
| Whack is the answer! I had recently set it up as a desk accessory.
I find it handy to be able to switch quickly between Uniterm and
Whack (they each have their specialties) and the DA made it real
easy. Well, since the DA never exits it keeps the interrupt vectors
modified forever.
Guess I'll have to go back to using the PRG version of Whack instead.
:-(
Thanks for info,
Dan
|
118.5 | I'll put it on my list | PRNSYS::LOMICKAJ | Jeff Lomicka | Fri Jun 10 1988 11:19 | 5 |
| Whack rarely uses the right button - I will see if I can arrange for
this "feature" to be off most of the time, and turn it on only when the
window with input focus is using the right mouse button. (Not an easy
change, but well worth the effort, I suspect.)
|
118.6 | Thanks for your support! | RAINBO::COUTU | He who will not risk, cannot win. | Fri Jun 10 1988 17:51 | 6 |
| Sounds like a good idea, until then I'm using the .PRG version and
will keep an eye out for your postings about Whack.
Thanks,
Dan
|
118.7 | Different methods? | LDP::WEAVER | Laboratory Data Products | Fri Jun 10 1988 18:31 | 6 |
| Re: .5
There is some code that Atari has made available which makes both
buttons work, I will see if I can find it and send it to you.
-Dave
|
118.8 | Two buttons are better than one | MILRAT::WALLACE | | Mon Jun 13 1988 13:32 | 8 |
| Dave,
Sounds like something more than one of us would be interested in.
So could you either post it here as a reply (if it's short) or make
it available for copying?
Thanks,
Ray
|
118.9 | When a solution is not a solution | PRNSYS::LOMICKAJ | Jeff Lomicka | Wed Jul 20 1988 13:32 | 6 |
| I got the "official" two-button patch from Dave, and was disappointed
to find out that they use the same method I do. Using the Atari code
would have the same drawback - desk accessories would see both buttons
as the left button.
Back to the old drawing board.
|