Welcome back MadAngus. As long as it's only the kitchen that gets plastered.
(There should be a smiley for really bad jokes.)
Congratulations on a successful move and settling in. The stress of moving house is reckoned to be second only to a Guru Meditation error. (There really, really should be a smiley for naff comments too.)
I'm still up to my neck in stuff and spending as much time revising the docs as doing the programming. There are some significant errors in the manual and help files as to how things really work. Nothing like a bit of programming to sort out the problems.
As I'm working in WINUAE on a PC, I now keep using Amiga keyboard shortcuts in Windows and wondering what went wrong. A bit like the tablet users who try to expand a newspaper picture with their fingers before they realise what they're doing.
Did anyone spot the deliberate mistake (my excuse) in my last post? Of course (sic) it was the BOx instruction syntax:
BOx x 0, y 0, fimage 1, w SizeX, h SizeY;
It should have been:
BOx xs 0, ys 0, fimage 1, xe SizeX, ye SizeY;as it uses xs, ys, xe and ye (start and end corner coords, not start corner, width and height as the manual and help files state). Just one example of why this is taking a while (excuses, excuses). But I think you'll find the atention to detail worthwhile in the end. (There will be questions later...)
Didn't miss out on the annual 'flu epedemic here, but it didn't knock me about too badly.
Switched to a full menu for the DBL Expander/Editor as there were too many options for the space available in a gadget interface. So the menu docs are getting their workout too now. Menus are tedious, but the end result is worthwhile. A pity the Menu Editor accessory doesn't write to a Menu Bank, as that format isn't documented anywhere (not that my feeble search capabilities can find anyway). Some of it's understandable (pointers mainly) but it looks like I'll have to delve into the code to find out what's what. Another project for later unless anyone's already documented it?
A last few bits and pieces yet to go into the program. I.e. just realised it would be a great help to add a save format that produces merge code (in ASCII) for a DBL program. It can then be merged straight into your program for fine tuning without having to constantly save and reload into a bank. You can then just save the resulting string to a file for import into the Resource Bank Maker for the final program. The merge code format is simply:
A$="blah, blah, blah;"
A$=A$+"more blah, blah, blah;"
A$=A$+"etc, etc;"PS asymetrix - your post just came through while I was typing this - Fantastic - I've been looking for that book everywhere!