Recently Browsing 0 members
No registered users viewing this page.
PSPad4AutoIt3 consists of the Editor PSPad and the Improvement Kit, and can be used as an portable Editor IDE for AutoIt3.
The author of the PSPad Editor is Jan Fiala. I (Professor Bernd) am only the author of the Improvement Kit.
After months of work, PSPad4AutoIt3 version 1.0.0 beta is now ready.
I like to call it the "first real" version, because the Improvement Kit now handles a lot of things autonomously. So PSPad remains operable when an au3 script is started. Also there is now a setup that makes the installation easier. 👍 And for those who don't like/do not want an installer, there is a download without setup. Without setup, the user has to take care of the prerequirements himself. Only recommended for experienced users.
The core functionalities "Run, Check Syntax, Compile and Comile Dialog" are integrated and work very well. Thanks to @Jos for extending AutoIt3Wrapper! There are also a few more features that you can find in the main menu, menu item "Scripts" => "_AutoIt". These include "Debug to Console", "Debug to MsgBox" and the "Koda FormDesigner" as a helper for creating GUIs. In this menu there is also an item "_Tips and shortcuts". After a click the AutoIt-relevant shortcuts are displayed.
The language in the menu "_AutoIt" is English. The language for PSPad in general can be set for more than 40 languages (Main menu => Settings => Program Settings => Language).
PSPad4AutoIt3 is in a beta stage and does not have many features yet. But I am working on it!
More information (EN, DE) and the download can be found in my PSPad4AutoIt3 Projekt in the AutoIt.de forum.
I would be glad if you have a look at it and write me your opinion. Have fun!
2020-04-20 Important note: The minimum version for AutoIt3 HAS TO BE 220.127.116.11!
I had hoped that the changes would not be so severe, so in the downloads the minimum version 18.104.22.168 is still indicated. Unfortunately, it has recently become apparent that with older versions the main functions, e.g. CompilerRunner, the AutoIt3 Help and the upcoming CallTipViewer, fail.
The downloads can be used so far, but everybody has to take care of the AutoIt3 version 22.214.171.124 by himself!
Thank you very much,
i suggest to set default encoding in Scite4 for Autoit 3 to UTF 8 with Bom encoding, format recommended also in Autoit Help.
In last editor version, when i open new script, for example Czech characters (č, ř, ž) aren't correct.
So when i change Encoding to UTF 8 with Bom from Default Code page property state, everithing seems to be OK.
Thank you and sorry for potentialy duplicated content.
What's new section:
Snowman_Sky is game using MapIt engine. MapIt will evolve here for a little bit.
Download: [ http://songersoft.com/programming/Snowman_Sky.zip ]
Video demonstrating new sprite_sheet class and weather effect.
Working on the Class section of the Character Sheet.
Which is what makes multiclassing possible.
Changing the value of Class will load the stored value for XP. Lvl will be updated to the XP tier.
Hit points are then rolled for each level of all learned classes. Hit dice are specific to each class and a Constitution modifier is added to each roll of hit die.
Im trying to launch a .exe file that is nested within the program files (x86) folder structure. i have already used the standard RunAs Syntax and found that it fails to launch the application. I have switched to Run and that seems to work. My issue is I have to use RunAs as the applicaton would need to run under a completely different account. The Current logged in user is a Local User on the machine, however, the application must be run as a domain user. The Machine is domain connected.
have tried the following:
RunAs("username","logonpassword", $RUN_LOGON_PROFILE, "D:\Program Files (x86)\Vendor\Application Name\Exe Location\Executable.exe") The above fails to launch, there are no errors or syntax issues, it just does nothing when the variables are replaced for the correct values.
I did the same using the Run command
Run("D:\Program Files (x86)\Vendor\Application Name\Exe Location\Executable.exe") That seems to work fine, but runs in local user context. Any thoughts? Could it be a local Machine rights issue? Or have i missed something glaring in my script