Just wondering if there's an option to sort these little niggles I have and which I may have missed. I realise that Amos is an old man of it's time, but I constantly find myself at odds with these small issues -
1. Use the cursor keys/mouse wheel
- Just what it says. It would be nice to be able to use the cursor keys within the editor to navigate about. I noticed the cursor keys at least can be used in Amos for windows but not in the version I have. Also, using the mouse wheel to scroll up and down would be a godsent, although I'm not sure the Amiga even had mouse wheels back then.
2. Use windows cut,copy and paste shortcuts
- Again just what it ways. Using ctrl+c for cut when I'm used to it just copying is hard to come around to, as is the ctrl+S and ctrl+p. If there's a way to make it the standard ctrl+c for copy, ctrl+x for cut and ctrl+v for paste that would be so good. Also, the ever needed ctrl+Z for undo would especially suit me and my bunging fingers.
3. Remove the *.abk when loading or saving banks
- Every time I go to load or save a bank I have to manually delete the *.abk from the file path in order for the bank names to show up in the window. I used to just type the bank name in manually, but I ended up with a few duplicate banks due to typing errors that way so I'd prefer just to click on the name but it'd be nice if they were just shown instantly.
4. Return to same point in program after exit to editor
- The editor seems to always go to the line where the program was exited and not to the line which you were last at before you started the game. I find myself navigating through the code quite a lot trying to get back to where I was. Is there an option to set that will make Amos automatically remember where you were before running the game? I see that there are user marks which can be manually set for specific places, but doing this every time seems unproductive. Even if the position of the cursor was logged before the game was run and then push a button to return to whatever that position was would be great.
If there are already solutions to these issues then I apologise, but it would make the world of difference to my workflow if there was.
Thanks.