Reaction first encounter

@Rigo & nbache

Yeah of course, a busy pointer would work. I never thought about the fact, that there is no such thing as a disabled window in any os, it never crossed my mind. But you are right, it would be confusing to the user.

@Rigo
Quote:
Agreed, but blocking input to a window is not strictly speaking exactly the same as keeping it deactivated/unfocused. Even if you block the window like you describe, it could still be activated and visually signal this (by a coloured border). The way I read Alfkil's intent, it should be kept (visually?) inactive. I don't know what purpose this would serve, but I guess there could be very special situations where this would be the logical GUI behaviour, and if so, my description might show one way of forcing this behaviour.

Best regards,

Niels

@nbache

The reason I wanted this feature is, that I'm using lots of different windows in db101 and some of them, when open, allows for features, that needs other windows features to be disabled. I could manually turn off the gadgets in those other windows, but it would be so much easier to just block the entire window (or it's content, rather), and then have it's state automatically restored when the "dangerous" window is done and the old window is un-disabled.

But I guess I'm just going to have to handle it the old way.

@alfkil

In that case you can use WA_ToolBox, TRUE.

It might be an idea if you reread the autodocs again to catch what you missed the first time :)

Simon

@Rigo

Quote:

In my version of the autodocs, this attribute doesn't have a description. Besides, it's a fairly odd name for such a feature, don't you think ?

@alfkil

The idea is that a toolbox window is used to allow the user to select some action or option without the window visually getting activated, which in turn saves the user having to reactivate the original window.

I'm surprised there's no description for this in the public autodocs.

Simon

@alfkil

It's described in intuition.library/OpenWindow()

@alfkil
Quote:
Make sure to refer to the intuition.doc when talking about WA_#? tags. WINDOW_#? tags should be described in window_cl.doc.

@ssolie

Sorry, I was looking in the window class only.