Leaderboard

Hi guys! It´s update time! ISN AutoIt Studio version 1.03 is online NOW! Changelog: (translated by google) -> ISN AutoIt Studio: <- ----------------------------------- - Bugfix: Various bug fixes - Bugfix: Tidy Source can now be added again to the toolbar - Bugfix: The automatic inserting of the $ character after Global, Local etc. (if activated) in comments is now always deactivated. - Bugfix: Icons of new controls were not displayed in the script tree of the ISN. This is now fixed. - Bugfix: When writing "," the parameters should be displayed correctly in Autocomplete. - Bugfix: Editor mode now works again correctly. (For example, no more macros could be created) - Bugfix: "Start Scripts via the AutoIt3Wrapper" now functions again normal - Bugfix: The dbug tool should now work again - Bugfix: As soon as a parameter with the character "(" was created in the parameter editor, any content in the listview disappeared immediately. - NEW: Many windows in the ISN can now be enlarged or maximized as desired! - NEW: The ISN is now optimized for monitors with high resolution (High DPI)! Furthermore, you can select any DPI scaling factor in the program settings under "Display"! - NEW: When testing the project, open files are saved only if something has been changed. The whole also applies to compiling, tidy, syntaxcheck, and compiling the macro file. - NEW: When creating a new file, umlauts (äöü) are now renamed automatically. (Ae, oe, ue) - NEW: The "ISN AutoIt Studio" logo at startup can now be moved with the mouse. - NEW: The Macrotrigger "Compile Project" and "Compile File" have been renamed "Compile After Project" or "Compile After File". In addition, there are 2 new triggers: "Compile Before Project" and "Compile Before File". - NEW: The Macrotrigger "Compile Before File" and "Compile After File" now also work for the "Compile Project" menu point as well as for each additional file compiled. -> ISN Form Studio 2: <- ----------------------------------- - Bugfix: Various bug fixes - Bugfix: Fixed some translation errors in the English version. - Bugfix: Alignment lines "dock" now only to controls, which are also on the same tab page as the control to be moved. - Bugfix: Bug fixed, which means that the FormStudio 2 was not started correctly. - NEW: Now you can double-click on controls. The action for this can be defined in the settings. Default is here open the extracode. - NEW: Direct application of extracode to the GUI design process can now be deactivated in the program settings. - NEW: Many windows in the FormStudio can now be enlarged or maximized as desired! - NEW: The FormStudio is now optimized for monitors with high resolution (High DPI)! - NEW: New Control: Toolbar (_GUICtrlToolbar_Create). Since a toolbar can be quite complex or dynamic, an editor (such as for menus) was not included in the FormStudio. The toolbar should be "configured" via your script or extracode. - NEW: The text mode for a control now also affects the icon or image path. - NEW: The selected skin of the ISN AutoIt Studio can now also be applied to the FormStudio. (To maintain a uniform design) The whole is however deactivated by default, as this has unfortunately also effects on the controls in the GUI Designer. (And thus possibly making the design difficult) If desired, the whole can be activated in the program settings of the FormStudio. - NEW: In the GUI properties there is now an extra point: "Extracode before GUI". This code will be added before the actual GUI. This can be eg. Variables, custom includes (for complex GUIs), or other declarations in the GUI. - NEW: New Control: Statusbar -> Simple File Viewer: <- ----------------------------------- - Bugfix: Various bug fixes - NEW: The selected skin of the ISN AutoIt Studio is now also applied to the plugin. (To maintain a uniform design)

Fine when it works now Ah looks like i overlook your last edit. so: You missunderstand the text a little bit. It doesn´t meas to "test a project". It measns the ISN contains a example project..or call it a demo. (and its called "test project" :P) So when you look under "all projects" when the isn starts you should see the "test project" (if you checked it in the first start dialog) If you don´t have the test project in your project list, you can create it in setting -> General -> Advanced -> Create test project. So the test (demo) project shows you an AutoIt Example with an integrated .isf Form. (The .isf is included directly in the script) So try it and just open the .isf file..make some edits in the GUI..and save it. (No code copy/paste) You will notice, when you run the mainfile (F5) your changes are allready there! That is what the messagebox weans..you don´t need to generate the code and copy/paste the whole thing. You simply need to include the .isf in your script and show the GUI via GuiSetState. (As in the testproject) Hope it helps you

You can find the path in the devug log of the isn. (Settings > general > advanced > debug. Path to config.ini) Search an open this file..find the ini keys and edit them. It sould work

You're welcome!

Hi! Really thanks for your video! I just released a hotfix update. Please check in the ISN for new updates...it should find a new one. Please test it if the error is gone now. Thanks!

... that or better _SQLite_FastEscape() the variable.

set quotes to this part too 'Multi Variation' Saludos

Glad you liked the solution

This actually was strike 3 .. so 5 days unable to post in our forums and think about the future here. Jos

You will find a description plus a conversion function in the wiki: https://www.autoitscript.com/wiki/Excel_UDF#Date_and_Time

@MattHiggs, using the said registry key can be tricky. you have to maintain trailing @LF and empty string for target path (if you wish to delete rather than move/rename). _WinAPI_MoveFileEx() can handle that for you - read the help file carefully. occasionally i encountered issues with that, especially files located in the system32 folder. if reliability is a must, i'd suggest using a scheduled task to run at startup, as the local SYSTEM account, executing a simple batch file to: 1) delete the said folders 2) delete the task 3) delete the batch file itself in this order!

Seems you have missed a part of the forum rules not opening a new thread related to the closed one. So, last chance tp read the forumrules and sticking to them! Jos

yes it was solved I did 2 things I added #RequireAdmin and a sleep( 2000) )_Excel_open $oExcel = _Excel_Open(False)                 Sleep(2000) ; I added this sleep pause                 $datawb = _Excel_BookOpen($oExcel, $STORENUM)                 $datawb.worksheets("Black").Select                 $LastRow = $datawb.ActiveSheet.UsedRange.Rows.Count                 $mydata = _Excel_RangeRead($datawb, Default, "A1:AI" & $LastRow)                 _Excel_BookClose($datawb,$bVisible =True)

Atakan, just for your information. @ProgramFilesDir macro depends also how you start your compiled script. If it is compiled as x64 @ProgramFilesDir is C:Program Files, as x86 is C:Program Files (x86). The 64-bit version can only be installed when the os architecture supports x64 execution. Br, UEZ

This works in Windows 7: $objShell = ObjCreate("Shell.Application") $objFolder = $objShell.Namespace("C:\Windows\System32") $objFolderItem = $objFolder.ParseName("calc.exe") For $val in $objFolderItem.Verbs() If StringInStr($val(), "Pin to") Then $val.DoIt() Next