>>Just as long as you don't get any expectations that Inno will ever be a click & point shooter.

Ah, crap. You mean this is as good as it gets? :-)

>>I've seen that happen to many tools I once loved to use (written
>>by Central Point and Peter Norton and Quarterdeck - remember them?).

Careful, you're admitting your age here. . .


>>That's because you didn't ask here first - or took the samples from the
>>Wiki. I cheated - went straight for the Wiki and took my scripts from there.

Well, they never told me I could cheat . . .

>>>>Again, you make assumptions on how easy or difficult it is for
>>>>everyone to use standard keyboards
>>As in "just wanted to see if I can follow... can't".
Same here, but for much different reasons. A mangled finger on each hand, and some at least find it very entertaining.


Oddly, I'm having trouble with the file "gdiplus.dll", which is not in the Common\MS\VFP folder.


That's actually the part I love the best about Inno - this is all so simple and clear, no fancy "multipodial terrestrial parser" names for what everybody else calls a rake, layout of sections is simple enough, help IS helpful (surprised to shocked, in that order, I really was).

>>And I've learned Inno in two hours.
>
>Maybe that's the key. I've only worked on Inno for a total of half an hour. Check again when I'm up to your level. :-)

>>automagically
Great word. Your creation?

>>And later, the maintenance can be as much as editing the version line
>>somewhere in first section and pressing ctrl+f9. Done in a few minutes.

I literally compile a distributable about once a year any more, so I'm not sure I need such maintenance ease, but yes, that IS a good selling point.

>>At the end of the day, you can call it a day.
I usually call it a day when I get up. After the sun goes down, I call it a night.