Why No "on openGroup" etc message

Got a LiveCode personal license? Are you a beginner, hobbyist or educator that's new to LiveCode? This forum is the place to go for help getting started. Welcome!

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller

Post Reply
istech
Posts: 211
Joined: Thu Sep 19, 2013 10:08 am

Why No "on openGroup" etc message

Post by istech » Fri May 22, 2015 10:38 am

Hi All,


I have been using LC for a while now and use the groups feature quite a lot. However I find that we can use groups like a control or a card or even a stack. So I was thinking why would you not add the feature to have "openGroup" or c"loseGroup" messages etc. This would seem like a logical step to make. No?

Maybe I am missing something and someone can comment on it.

Thanks

Klaus
Posts: 14199
Joined: Sat Apr 08, 2006 8:41 am
Contact:

Re: Why No "on openGroup" etc message

Post by Klaus » Fri May 22, 2015 11:51 am

Hi istech,

check the "openbackground", "closebackground" and related messages in the dictionary! :D


Best

Klaus

istech
Posts: 211
Joined: Thu Sep 19, 2013 10:08 am

Re: Why No "on openGroup" etc message

Post by istech » Mon Jun 15, 2015 2:52 pm

Thanks Klaus,

Sort of what I was looking for. Looking for a message to be sent when a group become visible. Can not see much in regards to this.

Maybe you can add something I am missing as openbackground is only sent when you go to a card

Thanks

Klaus
Posts: 14199
Joined: Sat Apr 08, 2006 8:41 am
Contact:

Re: Why No "on openGroup" etc message

Post by Klaus » Mon Jun 15, 2015 2:53 pm

istech wrote:Maybe you can add something I am missing as openbackground is only sent when you go to a card
No, sorry, that's all we have.

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10052
Joined: Sat Apr 08, 2006 7:05 am
Contact:

Re: Why No "on openGroup" etc message

Post by FourthWorld » Mon Jun 15, 2015 3:59 pm

There's also an openControl message sent to any group when the card it's on is opened. If the group's backgroundBehavior is set it'll get openBackground first, then openControl. But openControl will be sent regardless of the backgroundBehavior, so it sounds like just what you need to allow a group object to initialize itself before being rendered for the user.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn

Post Reply