Showing elm full path
05-22-2023, 02:32 PM
1. How it can be useful?
2. If need an user-defined condition, use the *also* parameter. It's a callback function. Then replace .Find(1) with .FindAll(), and use foreach. In next LA version the 'Find UI element' tool will have new actions 'FindAll' for creating such code.
3. LA adds /// doc comments when you type /// above a function etc. When typing the '<' character, it shows an autocompletion list of tags. It works like in Visual Studio and VSCode. Do you suggest adding a tool like the QM2 "Function Help Editor" that inserts tags like <remarks>, <param ...>, <see ...> <b> etc in a faster way?
2. If need an user-defined condition, use the *also* parameter. It's a callback function. Then replace .Find(1) with .FindAll(), and use foreach. In next LA version the 'Find UI element' tool will have new actions 'FindAll' for creating such code.
3. LA adds /// doc comments when you type /// above a function etc. When typing the '<' character, it shows an autocompletion list of tags. It works like in Visual Studio and VSCode. Do you suggest adding a tool like the QM2 "Function Help Editor" that inserts tags like <remarks>, <param ...>, <see ...> <b> etc in a faster way?