Then you use the "Set - Dialog Item Image" action to set the image's image instead of the button's image. Make it slightly smaller than the button and set it in a separate variable that you can refer to. Variables allow you to keep track of a certain unit, a winning player, a type of unit or even text strings. You can store almost any kind of data inside a variable.
Variables play an important role in scripting because they enable programmers to write flexible programs. The way I do it is to create a separate dialog item(an image) and place it over the button. Variables are locations in memory that can hold values. You can set the button text and in the button text add an image but it's clumsy and looks bad. Basically, I've had problems getting an image to work for the buttons. Since there's been like 3 additional replies since I started writing this thread, it's easier for me to explain since I know what kind of button you want. There's dialog buttons and command card buttons.ĭialog buttons are created through triggers and are used to create custom menus and stuff. It depends on what kind of button we're talking about.Īs far as I know, there's two relevant buttons you might be talking about(excluding screen buttons since they're not really useful for anything since the dialog does everything they do but better if I recall correctly).
0 kommentar(er)
