As Sheet Dialog

Scott Morrow scott at elementarysoftware.com
Mon Jan 3 20:13:21 EST 2011


Hello Joe,

I use this approach for "fake sheet" implementations, too.  One thing to watch for:   enabling the group once you have dismissed the "fake sheet" will enable *ALL*  the controls in the group... including controls that might have been disabled before the sheet appeared.  One way to handle this is to loop through all the controls and record any that are disabled before showing the sheet.  That way you can restore it correctly after dismissing the sheet.

Scott Morrow

Elementary Software
(Now with 20% less chalk dust!)
web       http://elementarysoftware.com/
email     scott at elementarysoftware.com
------------------------------------------------------





On Jan 3, 2011, at 11:06 AM, Jan Schenkel wrote:

> I would go for this approach as well - for the simple reason that it avoids 'traversalOn' issues where the user could still 'tab' to a control and then press the 'space' or 'return' key to activate a button.
> Plus, disabled controls look slightly different, and combined with an opaque 'overlay' graphic that has a blendLevel of 80 or so, you can even set its background colour to convey a difference between regular (white), warning (orange) and error (red) situations and questions.
> Two years ago, I used this approach in a Java Swing application, and people appreciated it a lot - even if it was Mac-like UI element seeping into a Windows/Unix environment.
> 
> Just my 2 cents,
> 
> Jan Schenkel.
> =====
> Quartam Reports & PDF Library for LiveCode
> www.quartam.com
> 
> =====
> "As we grow older, we grow both wiser and more foolish at the same time."  (La Rochefoucauld)
> 
> 
> --- On Mon, 1/3/11, Marty Knapp <martyknapp at comcast.net> wrote:
>> What about placing everything that
>> will be behind your dialog into a group, then disable the
>> group when showing the dialog and enabling it when it
>> closes?
>> 
>> Marty Knapp
>>> Please, anyone...
>>> In my current app I'm attempting to mitigate the very
>> small text dialogs that appear in the Windows' version of
>> applications by rolling my own. Some Dialogs such as the
>> page setup present some major challenges to doing this, but
>> with others it's not really much of a problem; however, I
>> would like the ones that I do create make their appearance
>> as sheets. Can that be done? Also... I'm not using stacks
>> for these Dialogs. I'm just creating Text fields with
>> overlying buttons. The problem with this is that I need to
>> implement a method by which these "Dialogs" can be modal in
>> behavior. I am doing that by including a mouseUp handler in
>> the stack script that requires certain activity when a given
>> item is visible. Anyone have a better method of doing this?
>> Is there something already built in that does this?
>>> 
>>> TIA,
>>> Joe Lewis Wilkins
>>> Architect&  Director of Product Development
>> for GSI
>>> <www.glsysinc.com>
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage
>> your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
> 
> 
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





More information about the Use-livecode mailing list