E.g.:
Code: Select all
$d = "<xydata>\icons\--------------------------------------------x.ico";"
The 1024er way looks like this instead:
Code: Select all
$d = "<xydata>\icons\--------------------------------------------x.ico";"
Yes, I did it exactly in this way...highend wrote:$d = "<xydata>\icons\--------------------------------------------x.ico";
Code: Select all
foreach($icon, "dp|gvfset|qnstgl|vfset|home") {
$icons .= "$icon||:$icon<crlf>"; }
inputselect( ,trim($icons, '$icons'), <crlf>, 1+256+1024);
Code: Select all
! Scripting: Some toolbar button keys could not be used to refer to toolbar
graphics. This issue concerned buttons with various graphical states
(on/off, vertical/horizontal, and the like). Not exactly a bug, but fixed
anyway. Now all toolbar button keys refer to a button or a state of a
button.
Note that you can also explicitly show the icon for a particular state of
such buttons. These keys are no documented AFAIK, so ask me if you need one.
Ask me again later this year...klownboy wrote:Beta v19.10.0001 really does clean up the SC inputselect box quite nicely. It works great for menus like highend's recent script here viewtopic.php?f=7&t=19123. Though I'm wondering if it would be possible to clean up even further by having an option to not show the Search Box and possibly not show the Enter and Cancel boxes. They limit how narrow we can make the width of the display and for many cases like menus we can double click the entry to select/run it and it would be understood that selecting and hitting enter would run or make the selection and hitting escape would of course still cancel inputselect. I know I'm pushing my luck. Thanks.