AkelPad

KDJ ...
I admit it. I have this happening all the time.

My apologies, gentlemen; in next version of User Manual, I will see what I can do. I can avoid errors due to unknown registry entries for sure (oversight on my part), and probably handle INI files transparently. I will ponder this for next release...

And updatelogologo

in new version.

se7h wrote:And update Logo in new version.

Isn't that already done in User Manual? Was changed in v10.04.11 (April 11). I still haven't done it in Plugins Manual (revision underway), I know.

Where did I miss the new logo?

In my post above, just click on word logo

I did, but where should I put it in the Manual? Already in "box" image.

new version is more mature, place it on the box instead of old

se7h wrote:new version is more mature

I see slight differences, and the topic has been discussed on the Russian page. But gentlemen - I AM NOT RUSSIAN! and do not read the Russian pages (Google translate) on a regular basis.

Do not forget, please, that I receive NO notifications of ANY changes to AkelPad or plugins - ALL is gleaned from the forums, a time consuming task...

I will replace the image, however, in the next release. But note that until new icon is present in official AkelPad release, I will leave Instructor's current icon.

I guess that you are not from Russia

But gentlemen - I AM NOT RUSSIAN! and do not read the Russian pages (Google translate) on a regular basis.

that is why I warned you

To all,

The newest User Manual has been uploaded to my site - see here for links - and will be put on the AkelPad official site in the near future.

The box image has been updated to the newest logo, and all tools for manual settings (Appendix E) have been rewritten (and should behave "better") in reponse to previoius comments in this thread.

Cheers!

Now works perfectly. Thanks Surveyor.

KDJ wrote:Now works perfectly.

Be careful - Instructor has found a bug (I forgot something!) in INI handling when variable cannot be found. Use with caution - a fix will be posted in a day or two.

Update (late, same day) - bug fix done to INI handling of Appendix E tools. Newest version (10.08.02) posted to link - official posting by Instructor to follow (I hope!).

Surveyor
Good work; thanks!

It would be rather nice if you could keep the Microsoft bashing to a minimum as it only makes the documentation look less professional. To say that the Windows API documentation is sketchy is just plain silly. Escpecially when you consider that your own documentation regarding the scripting plug-in does not even include the object model of the plug-in.

keith wrote:keep the Microsoft bashing to a minimum

Could you please point out which sections you find offensive? I welcome your contributions to the documentation - it is a voluntary, user contributed effort...