[comp.windows.ms] Problems with Usher 1.1

nan@math.ksu.edu (Nan Zou) (01/24/91)

I downloaded Usher 1.1 eagerly and tried it on my computer. Then I encounter
some strange behaviors. I specify both the middle and right button to be
non-sticky button. But when I click either button, the menu stays up. 
The left button works fine. Anyone else has a similar problem?

							Nan

leoh@hardy.hdw.csd.harris.com (Leo Hinds) (01/24/91)

In article <1991Jan23.173647.22709@maverick.ksu.ksu.edu> nan@math.ksu.edu (Nan Zou) writes:
>I downloaded Usher 1.1 eagerly and tried it on my computer. Then I encounter
>some strange behaviors. I specify both the middle and right button to be
>non-sticky button. But when I click either button, the menu stays up. 
>The left button works fine. Anyone else has a similar problem?

I too ran into the "sticky menu" difficulties you mention ... the only 
solution I found was to select a window and then the menu would go away ... 
maybe there should be some way (double click any button in the open 
desktop and/or <Esc>) to remove the "sticky menu" ...

leoh@hdw.csd.harris.com         	Leo Hinds       	(305)973-5229
Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n
creireg ?!!!!!!? ... znlor arkg gvzr

jvg0956@uxa.cso.uiuc.edu (Jacob Vanmilgen) (01/24/91)

nan@math.ksu.edu (Nan Zou) writes:

>I downloaded Usher 1.1 eagerly and tried it on my computer. Then I encounter
>some strange behaviors. I specify both the middle and right button to be
>non-sticky button. But when I click either button, the menu stays up. 
>The left button works fine. Anyone else has a similar problem?

>							Nan

I found the same problem. Another strange thing happens when you
load usher as a shell.  When you first start an application by clicking
and holding the left button, the menu comes up and disappears right away.
A second attempt will solve the problem.  The same thing happens after
exiting a program and starting a new one.

Any suggestions?
Jaap van Milgen

george@hobbes.ncsu.edu (George Browning) (01/24/91)

>I too ran into the "sticky menu" difficulties you mention ... the only 
>solution I found was to select a window and then the menu would go away ... 
>maybe there should be some way (double click any button in the open 
>desktop and/or <Esc>) to remove the "sticky menu" ...
>

Sorry everyone's been having difficulties.  I'm trying to figure
out a fix for the sticky menus problem.

How to remove a sticky menu: use the *left* button to select an
menu item then "roll" the selection off the menu.  The menu
will go away.

The problem: The Windows function TrackPopupMenu, which handles
the menu after I bring it up, looks for left button events to 
select items on the menu.  This includes removing the menu from 
the screen.

I've tried a couple of tricks to fool TrackPopupMenu with little success.
But don't worry - I'll find something since (I'll admit) the current 
sticky menu implementation is kind of a pain.  Windows doesn't really
support "sticky" menus so I'm having a hard time.

A, potentially, bigger problem:  there seems to be some conflict
with Usher and QEMM when used in Real Mode Windows.  This seems
to be a QEMM problem since Usher works fine with HIMEM.SYS.
What's strange is that some users have had no problems using QEMM
with Usher and Real Mode!  Anyway, if you experience this problem 
please let me know (and report your system configuration please).
Try HIMEM.SYS and tell me if that fixes the problem.

Thanks for your support (and your patience),

george (Mr. Usher)


--
------------------------------------------------------------------------
| o |  George Browning                 george@catt.ncsu.edu        | o |
| o |  NC State University             Raleigh, NC                 | o |
------------------------------------------------------------------------

yogurt@mimsy.umd.edu (Rob Crittenden) (01/24/91)

> I too ran into the "sticky menu" difficulties you mention ... the only 
> solution I found was to select a window and then the menu would go away ... 
> maybe there should be some way (double click any button in the open 
> desktop and/or <Esc>) to remove the "sticky menu" ...

Clicking on another menu (or icon) will work, but I think I've found a
preferrable solution.  I wanted a title bar on all of my menus, so I just
put in an empty selection, i.e.:

    <Foo>=

This gives me the title Foo (I usually follow it by @LINE@= too) and if you
click on it, the usher menu goes away.  I suppose you could put at the end
of all your menus something like <Quit>= and get the same results and being
more clear at the same time, your mileage may vary.

-- 
+------------------------------------------------------------------------+
|  yogurt@cs.umd.edu         Robert              Comp Sci Dept, U of Md  |
|  uunet!cs!yogurt             Crittenden        College Park, MD 20742  |
+------------------- so much beer, so little time -----------------------+

george@hobbes.ncsu.edu (George Browning) (01/28/91)

In article <1991Jan26.233822.25218@vlsi.polymtl.ca> doctor@vlsi.polymtl.ca (Paul Do (News)) writes:
>
>I have ScreenPeace, Usher, and Raise loaded at Windows boot-time.
>
>After using applications fer a while, I see screenpeace starting its
>effects and I have no way of stopping it except for the BIG SWITCH.
>
>Would Usher be capturing keys that ScreenPeace can't see ???

Well, I tested Usher 1.1 with Intermission (the retail version
of ScreenPeace) and Raise with no problems.

I guess ScreenPeace uses one method to check for user activity
and Intermission uses another.

Not much Usher can do to fix that -- you could go buy Intermission
to replace ScreenPeace.  I'm kind of biased to that suggestion
since I helped write one of the screen savers in Intermission! :-)

george

--
------------------------------------------------------------------------
| o |  George Browning                 george@catt.ncsu.edu        | o |
| o |  NC State University             Raleigh, NC                 | o |
------------------------------------------------------------------------

akm@cs.uoregon.edu (Anant Kartik Mithal) (01/29/91)

In article <1991Jan28.132555.11484@ncsuvx.ncsu.edu> george@hobbes.ncsu.edu (George Browning) writes:
>In article <1991Jan26.233822.25218@vlsi.polymtl.ca> doctor@vlsi.polymtl.ca (Paul Do (News)) writes:
>>I have ScreenPeace, Usher, and Raise loaded at Windows boot-time.
>>After using applications fer a while, I see screenpeace starting its
>>effects and I have no way of stopping it except for the BIG SWITCH.
>>Would Usher be capturing keys that ScreenPeace can't see ???
>Well, I tested Usher 1.1 with Intermission (the retail version
>of ScreenPeace) and Raise with no problems.
>I guess ScreenPeace uses one method to check for user activity
>and Intermission uses another.

I am running screenpeace and usher together with no problems. I even
have backmenu running with usher on one machine.

kartik
--
Anant Kartik Mithal                                     akm@cs.uoregon.edu
Research Assistant, 					(503)346-4408 (msgs)
Department of Computer Science,                         (503)346-3989 (direct)
University of Oregon, Eugene, OR 97403-1202

cccstevn@barney (Steve Ansell) (02/13/91)

In article <1991Jan24.012814.19132@ncsuvx.ncsu.edu> george@hobbes.ncsu.edu (George Browning) writes:
>
>How to remove a sticky menu: use the *left* button to select an
>menu item then "roll" the selection off the menu.  The menu
>will go away.
>

   Another way to remove the menu, that also makes them look nicer, is to 
add a title to each of the menus.  Just add a line like:
	TITLENAME=
(alternately followed by)
	@LINE@=
This gives a title to the menu that can be clicked on like a normal label
but will produce no action other than clearing the menu.  Even with the 
problem with sticky menus, I still like them much better than having to
hold down the button as I traverse the menu heiarchy.
   One other problem that I noticed with Usher is that if I double-click on
another application (like an icon) then usher pops up after the scond click.
This is only a minor anoyance as it goes away again as soon is I click some-
place else.

						-Steven T. Ansell
						Unix Consultant
						Computing Services U.C.D.

pti4378@ritvax.isc.rit.edu (IGOE, PT) (02/13/91)

Could someone repost the result of the discussion on the problems with ATM and
Usher?  We just bought ATM and Usher croaked.

Thanks,

Pat