Control groups - different button labels per card

[rjenkinsgb]

Hi,
I have a nice auto-size toolbar working & set as a group / background so it appears on new cards.

However, despite hours of experimentation & google searches I cannot figure out how to have different button labels on each card with the grouped controls.
It does not matter which card or instance of the group I select, changing a button label changes it on all cards.

Is it possible to pre-define different labels on each card or do I have to consider it more like a softkey system where labels and actions are processed by a common handler for the whole application?

I have seen "in passing" mention on another site that the buttons in a group can have per-card properties, but I'm totally stuck on how or where you set these...

RJ.

[Klaus]

Hi RJ,

I have seen "in passing" mention on another site that the buttons in a group can have per-card properties, but I'm totally stuck on how or where you set these...

unfortunately LABEL or NAME are not per-card properties of buttons!
You will need to write some "preopencard" handler(s) to create the correct labels for your buttons per card.


Best

Klaus

[dunbarx]

Hi.

What Klaus said.

Fields can have "local" or "global" contents, based on the value of their sharedText property, but the labels of controls are "global". So unless you overlay a field onto a button, or create some other new composite control, then, as Klaus says, the only way forward is to load the appropriate information during navigation, based on data accessed in your own manner.

Craig Newman

[FourthWorld]

LiveCode is very fast.

Suppose you had a list of button labels as a custom property in each card, something like:

buttonName1,buttonLabel1
buttonName2,buttonLabel2
buttonName3,buttonLabel3
etc...

Then you could have a preOpenCard handler in your stack like this:

Code: Select all

on preOpenCard
  put the uBtnLabels of this cd into tList
  repeat for each line tLine in tList
    put item 1 of tLine into tBtnName
    if there is a btn tBtnName then
      set the label of btn tBtnName to (item 2 of tLine)
    end if
   end repeat
   pass preOpenCard
end preOpenCard

LiveCode can process hundreds of controls like that in a fraction of a second.

[rjenkinsgb]

What I've actually done is re-name the buttons to something generic, eg. Key01, Key02 etc.

I've only got four buttons at present.

There is no need to re-name them from card to card - it's easier to know what they are & use the same info in every card..

on preOpenCard
set the label of Key01 to "whatever it is for this card"
set the label of Key02 to "blah"
... etc
end preOpenCard

on Key01
[do the action for that button on this card - just the name of the command in the main program]
end Key01

on Key02
[do that action]
etc..


The only parts that need changing from card to card are the label texts and the actions / commands called when that button is used.
(Each button has an on mouseup that calls it's own name as an action).


I was originally thinking I would need a centralised handler, but as I started on the card scripts I realised that the way livecode messages work, a handler within each card would get the key actions first so they can be re-sent to do appropriate things with minimal code.