How to make the Tooltip in a button

Here you go

(defun display_custom_form ()
  (let (button form)
    ;; Define button with tooltip
    (setq button
      (hiCreateButton
        ?name       'custom_button
        ?buttonText "Click Me"
        ?callback   (lambda (_button _form) (info "You clicked me!"))
        ));setq button
    (setf button->hiToolTip
      "This message is displayed when you hover the mouse over the button
<p><font size='+1' color='red'>You can use HTML inside tooltips</font></p>
<p>You could even display images</p>"
      )
    ;; Define form
    (setq form
      (hiCreateLayoutForm 'custom_form "Custom Form"
        (hiCreateFormLayout 'main_layout ?items (list
            button
            ));main_layout
        ));setq form
    ;; Display form
    (hiDisplayForm form)
    ));let ;def

(display_custom_form)

thank you a lot! and can these codes used in skill?

TZ20240722725 said:

can these codes used in skill?

The code that Aurelien posted is SKILL.

Andrew

oh i get it!

thank you

HI Aurelien

I found that you wirte a lambda function with two parameters for button as it's callback, and I checked the user guide("skuiref.pdf") of skill language that is not mentioned the callback funtion of btn will pass two parameters, the first one is button and the second one is the form that putted. it's very helpful for me, thanks a lot.

Thanks,

James.

James,

Actually it does cover this in the documentation. In the section "Function Object Callbacks" it says:

Function Object Callbacks
The syntax of a function object callback is the following:
<callback> (o_field g_scope @rest_args)
where,
■ o_field is the field whose callback is triggered. It can be used to access the
properties of the field (o_field->value).
■ g_scope is the location where the field is instantiated. It can be a HI form, a scroll-
region field, or a page of a tab field. It can be used to access fields that are placed in the
same scroll-region, tab page, or form where the field (o_field) for which the callback
is triggered placed. To access the fields in the same form but outside g_scope, a
function is provided. The function name is hiGetFieldScope.

later in the chapter:

Function Object Callbacks with Additional Arguments
Function object callbacks in Cadence User Interface generally accept two standard
arguments o_field, which represents the field whose callback is triggered and g_scope,
which represents the location where the field is instantiated. Other than these two standard
arguments the callbacks of function object type for certain HI fields require additional
arguments.The following table lists such callbacks:

As button fields are not listed in the table below, they accept those two arguments for the callback.

Andrew

Thanks Adnrew, I found it. I will check the document.