Stats

  • Locked Locked
  • Replies 11
  • Subscribers 149
  • Views 7070
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

how to change buttontext/icon

mantis

test1 = hiCreateButton(
             ?name 'test1
             ?buttonText "test button"
             ?callback "println(\"hello pressed\")"

)

I want to change buttonText to any other words.how ?

and I find I can't access the buttonText attribute through ~> operator, why?

Parents
  • mantis
    hi Andrew,

    attachment is a small skill program.
    the program is willing to create a button matrix, the matrix is dynamic, can be changed by type in  X or Y .
    the button label can be change to the name in the list box by pressing the button.
    I get two question,
    1. how can the list box be dynamic, I mean I can update the list element by change the strlist in the program.
    2. the button callback, callback should be a string,  how I can do other action when changing the button label.
    I can create a procedure, but the button label will not change correctly.

    what about your suggestion?

    following is a snapshot of the program.




    Regards,
    Tommi.
    MC_procedure.il
Reply
  • mantis
    hi Andrew,

    attachment is a small skill program.
    the program is willing to create a button matrix, the matrix is dynamic, can be changed by type in  X or Y .
    the button label can be change to the name in the list box by pressing the button.
    I get two question,
    1. how can the list box be dynamic, I mean I can update the list element by change the strlist in the program.
    2. the button callback, callback should be a string,  how I can do other action when changing the button label.
    I can create a procedure, but the button label will not change correctly.

    what about your suggestion?

    following is a snapshot of the program.




    Regards,
    Tommi.
    MC_procedure.il
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.