AW: how to get back to browse tool via script?

Tiemo Hollmann TB toolbook at kestner.de
Mon Jun 11 11:27:30 EDT 2007


Thanks Eric and Ken,
I think I still have to learn a lot of Rev basics :)
Tiemo

-----Ursprüngliche Nachricht-----
Von: use-revolution-bounces at lists.runrev.com
[mailto:use-revolution-bounces at lists.runrev.com] Im Auftrag von Ken Ray
Gesendet: Montag, 11. Juni 2007 17:03
An: How to use Revolution
Betreff: Re: how to get back to browse tool via script?

On Mon, 11 Jun 2007 16:32:53 +0200, Tiemo Hollmann TB wrote:

> Hello,
> 
> I have a button to give the user the chance to choose the brush tool.
After
> finished the paint job the user should choose again the browse tool.  BUT
> with the brush tool active no button is triggert any more. Nor can I
change
> the tool back again automatically by "mouseenter", because mouseenter
isn't
> triggert either any more. What am I missing?

Well, the basic command to execute is:

  choose browse tool

But as to how you execute it, you have a couple of choices:

1) Make a menu item that changes the tool back to browse.

2) Make a palette with a button that changes tools (palettes always get 
the browse tool even if the toplevel stack has another tool, so you can 
click on palette buttons).

3) On your toplevel window create a button that will pick the browse 
tool and set its "cantSelect" property to true (this means that it 
can't be selected with the pointer tool and so that button is 
clickable). If you do this and you need to affect the button later, you 
turn off the cantSelect property of the object by script in the message 
box and then you'll be able to work with it normally.

HTH,

Ken Ray
Sons of Thunder Software, Inc.
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/
_______________________________________________
use-revolution mailing list
use-revolution at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution




More information about the use-livecode mailing list