AutoIt3Wrapper - "run" with stop on error by parameter

[Musashi]

Perhaps my statements were misleading, especially the use of the word "simultaneously" ?

In his post  Post  @Professor_Bernd describes problems if both editors are open and Ctrl+Break is used. I just wanted to confirm your statement : 

3 hours ago, Jos said:

Don't expect to be able to run a script both in SciTE and pspad at the same time with the same shortcuts as that is expected to give strange results.

I should have written more precisely :
"But as soon as the user has made the decision to work with PsPad instead of SciTE, there is actually no reason to open PsPad AND SciTE at the same time anymore."

1 hour ago, Jos said:

This doesn't currently work with just SciTE either!  

From the Helpfile SetHotKey():  ...

I'm aware of that .

[Jos]

The Second ran Autoit3Wrapper actually is unable to perform the HotKeySet() and a 0 is returned, so I will reflect that in the next version of Autoit3Wrapper to indicate it did fail and not show those shortcuts for Stop and Restart.

Jos

[Jos]

@Professor_Bernd,

I've played a little with the logic in Autoit3Wrapper for HotKeySet() and now only enable the HotKeys when the Editor that was used to start Autoit3 has the focus in the latest Beta version.
This allows multiple instances of Autoit3Wrapper in case one wants to test 2 scripts at the same time.

Jos

[Professor_Bernd]

Hi Jos.

I'm not at home today and should have left already, so just briefly: Please don't switch off the features of Autoit3Wrapper (VERSION = "19.102.1901.11"), because 99% of all functions work.

In CompilerRunner I don't use a HotKey! That's all Autoit3Wrapper does and it works great! 👍

Only Ctrl+Break doesn't work under certain, very rare circumstances that a user might never see.

- - - -

I'm just seeing your new posting and I'm happy about it!

But I have to leave now. I will be back tonight and will answer in detail.

Here the adapted AutoIt3_CompilerRunner.au3. Just replace in "...PSPad\Script\AutoIt helper scripts\"

There is no hotkey set, just a security check with "_IsPressed" (you can search in the script for "_IsPressed" to find my workaround).

Bernd.

[Jos]

57 minutes ago, Professor_Bernd said:

Please don't switch off the features of Autoit3Wrapper (VERSION = "19.102.1901.11"), because 99% of all functions work

Not sure I understand because I am not switching off anything, just doing some code cleanup and looking at things that are on my "checklist" since a while.
Just finished fixing the _RefreshSystemTray() Function as that was clearly not working anymore since a while and all dead icons were left in the System tray.
 

Jos

[Jos]

Just uploaded the latest beta version which now has all these changes applied:

- 19.102.1901.8-11 Changes to allow the program to be run by other editors.
    - 19.102.1901.12 Updates Stop and Restartconsole message to indicate in case the HotKeys aren't set in case of second instance
                     HotKeys are ony set when the Editor program has the focus to allow for multiple instances.
    - 19.102.1901.13 Updated _RefreshSystemTray, which wasn't working anymore since a long time
    - 19.102.1901.14 Added WinClose for the Shelled Script to nicely close that process before ultimately killing it when still needed. 
                     This avoids having dead icon in systemtray.

Jos

Edited November 17, 2019 by Jos

[Professor_Bernd]

@Musashi Many thanks for your posts.

@Jos I tested version 19.102.1901.14 and everything works fine. The output lands in the right editor, and the script for the respective editor is terminated.  For my work on PSPad4AutoIt3 it is important that I can work with SciTE and PSPad in parallel. That's why I'm happy that it works now.

That was good work! Thanks a lot!

...

I think PSPad4AutoIt3 is far, far from being a replacement for SciTE4AutoIt3. SciTE has been adapted for AutoIt for years, it has many features for AutoIt and many good people are working on it.

PSPad itself has been around for many years, but it's only been 2 months since I've been working on customizing PSPad for AutoIt. And I am only 1 man. If PSPad ever has half the features of SciTE, I'm happy! ... Until then it's my little project and it's just fun to develop and work with nice people in the forum.

Also Jan Fiala, the developer of PSPad, has already fulfilled some of my feature requestsfor AutoIt3. That's very nice and encouraging to continue.

 

Professor Bernd.

 

 

[Musashi]

46 minutes ago, Professor_Bernd said:

Until then it's my little project and it's just fun to develop and work with nice people in the forum.

That's probably the best reason of all. Regardless of what comes out in the end, your horizons have widened .

This thread also seems to bring some momentum into the general development of SciTE4AutoIt . Thanks to @Jos !

[Professor_Bernd]

Hi, Jos.

On Saturday I posted a download of PSPad4AutoIt3 for you in the forum. This was a "light" version to test my CompilerRunner with AutoIt3Wrapper. Unfortunately I mixed 2 versions in a hurry, so CompilerRunner was switched off and the old commands for AutoIt3Wrapper were used (F5 - F7).

Here is a (hopefully) correct version of PSPad4AutoIt3 'light' for Jos 2019-11-18 17.16.zip. You can see that CompilerRunner works by the fact that PSPad is operable even while AutoIt3Wrapper is running. (And you can see the additional icon in the SysTray.)   I tested it with AutoIt3Wrapper and the good result remains: Everything works fine when using SciTE and PSPad in parallel.

Since you installed PSPad in the Windows Programs folder, I have adapted my package. In the "ReadMe" are instructions where to put the files.

I'd be happy if you would test it.

Available shortcuts:

F1:            AutoIt-Help
Ctrl+L:        Log-Window show / hide
Shift+Ctrl+L:  Log Window clear

F5:       AutoIt3Wrapper "Run"
Ctrl+F5:  AutoIt3Wrapper "Check"
F7:       AutoIt3Wrapper "Compile"
Ctrl+F7:  AutoIt3Wrapper "Compile Dialog"

 

Bernd. 

[Jos]

I had only loaded the initial one you provided and everything was working fine.   
Merged the changes you have in this latest zip except making it a multiuser setup, so all config remains in the PSPAD directory as it was.
Tried all different options and all is looking goood except one minor issue: F1 opens both Autoit3 and Pspad helpfiles and pspad has Alt+F1 reserved for the language helpfile which is working fine. 

Jos

[Professor_Bernd]

Thank you very much for testing!

The following you know for sure, but only to show the details:

In Win 10 in the Applications folder no program has write permission. That's why every write operation is either rejected or redirected, depending on the software.

PSPad writes to INI files, so it can't store its INI files in the Windows programs folder. The standard installation (non-protable) creates a storage folder "C:\Users\<UserName>\AppData\Roaming\PSpad\" and in the Programs folder creates the "PSPad_MU.ini" which instructs PSPad to use its INIs in AppData.

If you turn off the multiuser setting in "PSPad_MU.ini" (MultiUser=0) then PSPad will use the INIs in the Applications folder. This works as long as the settings are read only. As soon as a setting is to be saved, an exception is raised.  Therefore it is better with a standard installation to enable multi-users and save the INIs in AppData.

If you don't want that (and at the moment I prefer that) you can use PSPad portable. Select any folder where you have write access and copy all files and folders from PSPad to it. Before starting PSPad for the first time, set MultiUser=0 in "PSPad_MU.ini".

Now no files outside this folder will be used. For example, I use several PSPad portables next to each other for testing purposes. If you don't necessarily need the standard installation of PSPad, I recommend the portable version. It's easier to use and easier to update.

This is just for explaining the background. I'm happy that everything works and that you tested my CompilerRunner!

Bernd.

[Jos]

Oh yes..fully aware how it should be, it is just how it was installed already and didn't want to change it, so simply changed the folder access to make it work for testing.

Jos

Edited November 18, 2019 by Jos

[Professor_Bernd]

6 minutes ago, Jos said:

so simply changed the folder access to make it work for testing.

Okay, that was smart!  Good work!

Bernd.

[Musashi]

14 minutes ago, Professor_Bernd said:

If you don't want that (and at the moment I prefer that) you can use PSPad portable.

I would always prefer to use the portable version. Unwanted side effects with already existing versions of PsPad are thereby excluded.
Even the download page of PsPad itself clearly states :
PSPad does not require installation, it can be simply unpacked into any directory.
[...]
Desktop and Start menu links, as well as system integration can be created later.
[...]
Everything is user controllable. The ZIP distribution does not contain spellcheck dictionaries, but these can freely downloaded and added later.

(BTW : User friendly solved by PsPad)

@Professor_Bernd :

Therefore you can provide a version of PsPad optimized for AutoIt (including modified Ini files), because this cannot harm other installations.

[Professor_Bernd]

Hello, Musashi.

You're right, I also prefer the portable version. Not having any side effects is a nice thing.

Actually, PSPad can be downloaded from developer website as portable version, but it only becomes really portable when the " PSPad_MU.ini" is created and you have set MultiUser=0.
 
That's why I keep saying for the portable version of PSPad4AutoIt3: DO NOT start PSPad before all files from my Improvement Kit have been copied into it! 

[Professor_Bernd]

Hi Jos.

Thanks for the new SciTE4AutoIt3 version 4.2.0. This makes version checking in my PSPad4AutoIt3 project easier than with the AutoIt3Wrapper.au3 versions.

Thank you very much.

 

[Jos]

7 hours ago, Professor_Bernd said:

This makes version checking in my PSPad4AutoIt3 project easier than with the AutoIt3Wrapper.au3 versions.

The SciTE version follows the same pattern as the official SciTE releases.
All other utilities have a generated versionnumber from the Date/Time it was made:

v19.1127.1402.0 _  0 = new release. Next Beta will increment this until next release.
 ++ ==-- ==--
  |  |     |_____ Time : 14:02
     |___________ Date:  -- Day 27
                         == Month 11
                         ++ Year 2019

Jos

[mLipok]

 

 

 

1

1 hour ago, Jos said:

All other utilities have a generated versionnumber from the Date/Time it was made:

v19.1127.1402.0 _  0 = new release. Next Beta will increment this until next release.
 ++ ==-- ==--
  |  |     |_____ Time : 14:02
     |___________ Date:  -- Day 27
                         == Month 11
                         ++ Year 2019

Jos

Is this any type of global standard like ISO or any other similar ?

[Jos]

This is what I selected a while back so it is easy to see the age of the version people are running, instead of a sequence versionnumber like mostly is used.

Jos 

[Professor_Bernd]

Hi Jos.

Thanks for the info, that helps a lot.

I thought to myself that block 1 is the year, block 2 is month and day, and in the end a sequential number that is increased with each beta. But I didn't think about the time in block 3. And if a part is missing, it's like an email address missing one sign: it doesn't work. 😁

So thank you very much for solving the riddle.