I often enough click on a dockie icon which instantiates a menu strip that I don't want.
How do you make it go away without choosing one of the applications or rebooting?

_________________
..effects of civilization upon...nature, the growing gap between what education was supposed to accomplish and what it consisted of, the national debt and...high taxes, the problem of the excess cost of medical care -- Philip Wylie, 1951

@ggw

Try right clicking in an empty space, might work.

_________________
X1000! Party on
Pure Gold
Hate tends to make you look stupid...

@ggw

Simply click again on the icon that opened the menu strip in the first place. On my system I have to wait about 2 seconds before clicking on the icon to make the menu disappear or re-appear or nothing happens.

Drewlio77

Last edited by Drewlio77 on 31-May-2012 at 06:53 AM.
Last edited by Drewlio77 on 31-May-2012 at 06:33 AM.

@Drewlio77

Quote:

Drewlio77 wrote: @ggw Simply click again on the icon that opened the menu strip in the first place.

Correct - assuming that when ggw says "dockie", he really means "Subdock dockie". Dockies can be many other things, e.g. a clock or a simple separator bar.

Quote:

On my system I have to wait about 2 seconds before clicking on the icon to make the menu disappear or re-appear or nothing happens.

This is the case for all icons in an AmiDock and is intentional; the delay is meant to "eat" any attempts to double-click a dock icon instead of starting the action twice in rapid succession.

Best regards,

Niels

@nbache

Quote:

This is the case for all icons in an AmiDock and is intentional; the delay is meant to "eat" any attempts to double-click a dock icon instead of starting the action twice in rapid succession.

I rather see it as a bug since the effect is more annoying than really helpful (once you've figured out that AmiDock works with simple clicks, which does not takes long...).
Technically speaking, when you double click on a dock icon, AmiDock sends a double-click event instead of a second simple click. So if the current code does not trigger on double clicks, this could explain what happens.

@Drewlio77

Yo' da' man! Thanks.

Do we (me) have to find out all these things by discovery only?

_________________
..effects of civilization upon...nature, the growing gap between what education was supposed to accomplish and what it consisted of, the national debt and...high taxes, the problem of the excess cost of medical care -- Philip Wylie, 1951

@ggw

Quote:

Do we (me) have to find out all these things by discovery only?

Not really but yes you do got a point as we need a better info system for all functions available in Workbench/AmigaOS.

but for now you can check Documentation and changelogs in the OS4 install.

_________________
Brand new website... www.amigaguru.com

@Drewlio77

Quote:

Simply click again on the icon that opened the menu strip in the first place. On my system I have to wait about 2 seconds before clicking on the icon to make the menu disappear or re-appear or nothing happens.

You have a 2 seconds double-click delay?!
I have closer to 0.2 secs Think I have 0.35 or something.

My key repeat delay is 0.16 secs and repeat speed is 0.015 secs which gives about one line of text per seconds in cursor movement. These two are about twice as fast as the fastest setting in winblows. I can't imagine using anything slower than this.

_________________
>Amiga Classic and OS4 developer for OnyxSoft.
>A1-XE/G4, Radeon9250, Sweex 5.1, SII680
-Don't hesitate to contact me about my programs, but please use e-mail instead of PM. E-mails are more likely to be read in time, and easier for me to keep track of.

@ggw

Quote:

Do we (me) have to find out all these things by discovery only?

Frankly I find it a bit facinating that you didn't try clicking the same icon again before writing a forum post...

_________________
>Amiga Classic and OS4 developer for OnyxSoft.
>A1-XE/G4, Radeon9250, Sweex 5.1, SII680
-Don't hesitate to contact me about my programs, but please use e-mail instead of PM. E-mails are more likely to be read in time, and easier for me to keep track of.

@Deniil715

Quote:

@Drewlio77 You have a 2 seconds double-click delay?! I have closer to 0.2 secs Think I have 0.35 or something.

The default setting is 1.5s and works perfectly fine for me at least (don't really see any reason to change it).

Quote:

@ggw Frankly I find it a bit facinating that you didn't try clicking the same icon again before writing a forum post...

+1

Last edited by salass00 on 01-Jun-2012 at 08:50 AM.

_________________
µA1-C - 750FX 800MHz, 512MB, 20GB HD, DVD-RW, OS4.1
Sam440ep - 440EP 667MHz, 512MB, 700GB HD, DVD-RW, OS4.1

@Deniil715

I think the reason I never tried that is that the sub docky is detached from the main dock, so I tried clicking around the sub docky. I remember trying by going to the [Edit Default Category] widget. Tried clicking between items on the main doc.

It did not occur to me that is was a TOGGLE /on/ the main dock.

It might be that I own no Bill Gates stuff, so if that was one of those "borrowed ideas" I would miss it since I haven't been steeped it /that/ stuff.

As in my last post, "Are we clueless ones just out of luck?".

ggw
PS. I don't have a single "12:00 blinking" item in the house. I have even been called to other houses in the neighborhood to make such "go-away". I guess we all have our blind spots (some of us have quite a few).

Last edited by ggw on 03-Jun-2012 at 11:24 PM.

_________________
..effects of civilization upon...nature, the growing gap between what education was supposed to accomplish and what it consisted of, the national debt and...high taxes, the problem of the excess cost of medical care -- Philip Wylie, 1951

@ggw

Quote:

I think the reason I never tried that is that the sub docky is detached from the main dock, so I tried clicking around the sub docky. I remember trying by going to the [Edit Default Category] widget. Tried clicking between items on the main doc.

I see your point and I must say I'm not completely happy with the behaviour either. I think subdocks should close on any click on the subdock itself or the main dock it was launched from (if configured to close on click). However, it cannot be closed by a click outside because then it would be very difficult to add icons to it from WB.

One bug that annoys the hell out of me is that you cannot right-click an icon in a subdock without first activating it. But activating is not possible since it will launch the tool of the icon. So one has to click on the icon and then drag the mouse off. Then it will be *invisibly* active and can take a right-click. Very annoying bug.

This docky system isn't completely thought through IMO.

_________________
>Amiga Classic and OS4 developer for OnyxSoft.
>A1-XE/G4, Radeon9250, Sweex 5.1, SII680
-Don't hesitate to contact me about my programs, but please use e-mail instead of PM. E-mails are more likely to be read in time, and easier for me to keep track of.

@Deniil715

Quote:

Deniil715 wrote: One bug that annoys the hell out of me is that you cannot right-click an icon in a subdock without first activating it. But activating is not possible since it will launch the tool of the icon. So one has to click on the icon and then drag the mouse off. Then it will be *invisibly* active and can take a right-click. Very annoying bug.

It is in fact possible, partly depending on the sizes and shapes of your icons, to find an area of the dock or subdock which is not covered by an icon, and activate AmiDock by clicking that. But it's usually not easy, and certainly not intuitive.

Quote:

This docky system isn't completely thought through IMO.

I tend to agree with you there.

One other thing I wish was possible is defining that a subdock is attached to a certain edge of the square covered by its subdock dockie icon (i.e. the place your click to open or close it). That would make sure it always followed it around, even if the main dock changed, thereby moving the docky icon.

This might also have helped in the above situation.

Generally (not only in the context of AmiDock), it can also be limiting that X/Y positions always have to be stated and understood as offsets from the left and top edges. I wish we could e.g. use negative numbers for defining offsets from the right and bottom edges, this would make it possible to "layout" our WB and applications much more flexibly, e.g. by having a window open or an icon position itself near the right edge of the screen and stay there even when switching resolutions.

Best regards,

Niels

@nbache

Quote:

One other thing I wish was possible is defining that a subdock is attached to a certain edge of the square covered by its subdock dockie icon (i.e. the place your click to open or close it). That would make sure it always followed it around, even if the main dock changed, thereby moving the docky icon.

You may give SmartButton docky a try then. SmartSubdock adresses this issue by dynamically positioning its child dock.

@Deniil715

There may be something with the coder's implementation that makes it difficult to do but what may have been better is to only prevent double clicks on the dockies that don't open other dockies. I agree it would be annoying to accidentally open a program twice but opening and immediately closing a sub-dockie is less annoying and a learning experience. It also is less confusing then when the docky won't close when accidentally opened and you wish to close it immediately. Though I just notice that the Window's start icon ignores the double click on opening (though not closing).

Sadly, regarding the ignoring the RMB, it is probably an artifact of the Amiga Intuition system. The RMB is generally tied to the active window and the sub-docky is not active so it never hears about it.

The alternate way to handle this would be to handle it through commodities. The only problem is that you add yet another program that looks through the screen and window list to determine which window the pointer is over. This is done during the input chain context; which you don't want to slow down with too many things. That is also how the autopoint commodity works.

I wrote a commodity called mousezone that replaces the need for multiple commodities looking through the screen/window list. Programs like autopoint then need only add themselves to the list of watchers that mousezone services. Dockies programs could do the same so that they could service a RMB click over them.

One of the reasons I wrote mousezone was to allow - among many other things - the pointer to change when it was over zoneclass areas. I discovered that although the pointer does indeed change; it only changes when the window is active. Again this is an artifact of the Amiga Intutiton system. The only work-a-round to get around this at the moment may be to forcibly change the window pointer of the current active window - even if it isn't ours - and then change it back when it becomes inactive. That may be fine as long as the window remains in existance - which I don't think can be guaranteed. I made sure to make it that zone class friendly windows wouldn't close while their zones were being communicated to. I illegally use one of the Windows bits to ensure this.

This could certainly help the dockies system do what you want. I think I've sent this code to someone at Hyperion. Hopefully they will incorporate it and maybe they can 'fix' the pointer situation.

Last edited by gonegahgah on 06-Jun-2012 at 01:40 AM.