[Interest] Multiple windows app modal?

[Alex Malyushytskyy]

It might be different guidelines for different system, but
the only restriction I would expect from top level disabled window is that
it cannot receive input from the user.
And it is supposed to be able to become active cause you might need to move
the window.

If in your case it seems unreasonable you may play with focus policy
(change it on top enablining/disabling) , overrode focusIn, focusOut
function or install custom event handler.

Regards,
    Alex

On Tue, Mar 12, 2013 at 1:16 PM, Scott Aron Bloom <scott.bloom at onshorecs.com
> wrote:

>  By looking at the attached.. I would be confused by the “grayed out”
> buttons on the graph windo…
>
> In general, having a window you cant close, or minimize or move (all
> available by a windows menubar menu) would be disconcerting…  Thouigh you
> could try changing the window constructor windows flags to get a different
> type of title bar to satisfy your needs.. There is a windows flag
> demo/example in the Qt distro to play with.****
>
> ** **
>
> But what I mean, is for the top level widget, have a single frame child
> that is vertically (or horizontally) layed out  with zero margins.  And
> name the QFrame.. If you then frame->setEnabled( false) all children would
> be disabled.****
>
> ** **
>
> You may need to change/update the style for the disabled children to NOT
> look disabled.****
>
> ** **
>
> scott****
>
> ** **
>
> *From:* John Weeks [mailto:john at wavemetrics.com]
> *Sent:* Tuesday, March 12, 2013 12:48 PM
> *To:* Qt Project
> *Cc:* Scott Aron Bloom
>
> *Subject:* Re: [Interest] Multiple windows app modal?****
>
>  ** **
>
> Thanks, Scott. I appreciate the thoughtful comments I've been getting. I
> think by now I know about enough about Qt to be dangerous :)****
>
> ** **
>
> On 12-Mar-2013, at 11:27 AM, Scott Aron Bloom wrote:****
>
>
>
> ****
>
> Rather than disable the window (which I could see the being tons of
> reasons not to do)****
>
> ** **
>
> Could you elaborate?****
>
>
>
> ****
>
> why not just disable a top level background frame or group box?
>
> ****
>
> ** **
>
> I'm afraid I don't quite understand. The windows in question are top-level
> windows (that is, real OS windows).****
>
> ** **
>
> In case it's of interest:****
>
> ** **
>
> I have attached a screen shot of a demo of the feature. It happens to be
> taken on a Macintosh, but could be on Windows. Hopefully one day it could
> on Linux.****
>
> ** **
>
> The window labelled "Pause for Cursor" is a window created by user code.
> In a real application, our users often create wonderfully complicated
> panels packed to the gills with various kinds of controls. The idea here is
> that the circle and box markers on the graph indicate a region of interest
> in the graphed data. The control panel waits for the user to adjust the
> positions of the markers; when the user clicks Continue, analysis code
> (also user-written) can analyse the marked region of interest.****
>
> ** **
>
> There may be other graphs, tables, and other kinds of windows present.
> Think of our application as a "numerical analysis IDE".****
>
> ** **
>
> -John Weeks****
>
> ** **
>
> ****
>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20130312/8a2efe08/attachment.html>