Custom Query
Results (136 - 138 of 3876)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #137 | Rejected | Syntax highlighting for custom function names | Jos | cyberempires@… |
| Description |
Have the scite4autoit highlight the custom functions in a script I recommend the color DarkGreen: R53, G153, B70 |
|||
| #138 | Rejected | Ability to add custom helpfile values | anonymous | |
| Description |
Lets say that person Y makes a script they could also use this to have there function installed into the #include folder as well as the help file. |
|||
| #139 | Rejected | window identification / fixing current window | _alexei@… | |
| Description |
Currently, AutoIt can not guarantee keystrokes sent by Send would go to the particular window. Focus may change because of many reasons (other app. activity, system popup, user interference, etc.) There is no simple way to find a window with particular relation to already known window in terms of child/parent/sibling/owner of any level, also, verifying window class and other properties. That's pretty easy to implement by verifying each window in Z-chain against specified properties and relations. I want to be 100% sure AutoIt clicks the button (or sends keystrokes to the window) it was programmed to. Bottom line: util window identification becomes reliable, AutoIT is just a dangerous toy, unsuitable to serious applications. BTW, "special treatment" of controls creates unnecessary limitations, as controls are just windows with specific relations to the parent/owner. |
|||
