Family Historian User Group

If any one uses PSPad the latest version support the code explorer on Lua scripts so you can get views like this of plugin source:



You can download the latest version from:

http://www.pspad.com/en/download.php



ID:6748

To get it to work the Highlighter for Lua must be invoked as follows:
Use Settings > Highlighters Settings
Select a box on the left.
On Specification tab User Highlighters on right select Lua and click OK.

Files must have file extension .lua and may need to use Tools > Code Explorer window to enable tools.

You can add. fh_lua to lua in the settings so it works directly with plugin files

The procedure in PSPad is:
In an Administrator account open PSPad.
Use Settings> User Highlighter and Load the Lua.INI file.
In File Types, Comma Delimited at the top add ,*.fh_lua and click Save.

You may need to re-apply the Settings > Highlighters Settings as above to get the change to take effect.

I will add these guidance notes to the FHUG Downloads for PSPad.

Didn't want to start a new topic, but I found PSPad not much worth it.
It got 99% things unneeded but misses something essential such as inbuilt debugging facilities or at least a LuaShell so one could try something before finalising a line of code after one worked out if it does what one expects.

At the moment my personal favourite is the wxLuaEdit from the wxLua distribution. It's neary as simply as the internal editor FH offers (first view) but surprised me with it's stack capabilities and offers syntax highlighting.

2 drawbacks which set it down a bit.
If you add fh api keywords to the highlighter and press Apply ... don't forget to save the settings before quitting the program. Since otherwise you'll have the experience to see if you're faster when doing the same job the second time.
And for Win7 users, the open file selector can't reach for hidden folders (c:programdataCalico PiePlugin) so you either have to do to 'subst' (you remember that from when you were young do you? MS DOS 3.1 feature, or find any other way you might know youself.

But while at editors ...
Why do all the dlls within the FH program not follow the original namings? iuplua.dll is named iuplua51.dll, same for iuplua_pplot(51) and some others.
Since to prevent version conflicts I found that it's anything but clever to install a complete lua dll system besides the one from within FH, since then one might have working code but not working within FH.

Why do all the dlls within the FH program not follow the original namings?

I think you will find this is the correct us of the Lua level in the dll name.

PIL and the Lua Reference manual cover this in detail