MK3 for A1200 - 'flashtool info' still says v1.0

The firmware and flash tool have different version numbers. So it's expected that firmware version number is not identical with the config tool version number. We might change that in the future, but for now, while the config tool isn't even feature-complete, there's no point in creating confusion between our own developers

It's more complicated than that.

The flashtool reports its own version, which is not necessarily in sync with the config tool's version.

Also it reports the flash chip's Id and version, this version is currently 1.0. So we have four versions:

- 'IndivisionAGAmk3' config tool: version is currently 1.x

- flashtool: version is also 1.x, similar, but not necessarily the same as the config tool

- FPGA firmware: version is in ISO-date format, e.g. 20200812

- flash: this version is currently always 1.0.

As feedback for developers I also suffered some frustration as I had no idea how to flash the firmware in the GUI. I used the shell method instead, which was a little more scary but worked. No where is there a mention of right click menu in the docs, it would have saved me some stress

But overall thank you all for your hard work, I am exceptionally pleased and Icomp has never let me down (fairly new to Amigas, have 1233n Accel and now agamk3)

Quote from JaimieV

Useful: Backup the current settings config to a file, which can be pushed back later or shared.

This is already in the config tool. The file is even human-readable, so you can extract single screenmode entries with a text editor and share them in a forum if you like.

Quote from JaimieV

And of course specify "right click menu" in the docs

The term used in most Amiga software is "drop-down menu". However, the general term "menu" has always been associated with the drop-down menus in Amiga software. It would be rather boring if each and every program would re-explain how to use Amiga menus. After all, we're working with a retro system, and that's how the Amiga developers thought a program should be handled. While the config tool already guides the user by enabling and disabling buttons under certain conditions (which is really complex!), the look&feel of the computer shall not be changed. We should not attempt to imitate the look&feel of a modern smart phone

Quote from JaimieV

Or move the few right-click menu functions to buttons? There doesn't seem any particular reason to hide them in a menu.

The reason is that the tool shares a common code base with the Indivision ECS V2 config tool. That is supposed to work with an un-expanded A500 using NTSC non-interlace screen mode, limiting the window size much more than you are limited on an AGA system.

During development of the AGA MK3 flicker fixer, this code base has gained lots of subtle changes that guide the user, and these shall of course be available to Indivisino ECS V2 customers at some point. Breaking with the layout restriction would not let us back-port the changes, which would be really unfair, as the existing Indivision ECS V2 code base has reduced the cost of development for the AGA MK3 version considerably. I believe that such benefits should go both ways.

Hi Jens, JamieV & me just suggested to specify where to find the firmware flash in the docs. Not to change your GUI. This is to reduce the stress of your users, and the stress of yourself when you have to answer questions in the forum. I hope you understand what we mean.

Thank you for your suggestions, they are duly noted.

Please prefer the GUI, not the shell method, it's so much easier and less error-prone to flash the Firmware from the Pull-Down menu. Also when you click the "Flash" button in the GUI dialogue, the current configuration is automatically written back after flashing the firmware. When flashing using the commandline tool, a power cycle is likely needed and the configuration still needs to get written back.

You can already save a configuration using the menu item 'Project/Save As...' and load it later using 'Project/Open...'.

You can see the FPGA version in the OSD. For example, select a different Indivision mode and click 'Test/Adjust' to see it.

(Ok, it might be a good idea to produce the OSD always on entering the Test/Adjust screen.)

No problem - suggestions are welcome, but of course we can't fulfill each and every wish. Documentation must stay readable, handling must stay "Amiga-like", and any change must remain consistent with the overall concept, as there's quite some thought in it - more than it may look at first sight.

So let me make clear that I wasn't trying to fend off "any" change of the config tool - I was merely explaining the limits of possible changes, as we are not only looking at one, but two products (AGA MK3 and ECS V2). If you don't already own an Indivision ECS V2, this explanation is really required, otherwise you don't understand the limit in window size.

I do admit that the long text in the Wiki could use some illustrations - these may make clear(er) how the flicker fixer works, and what the settings do. I guess that illustrating the location of a setting in a block diagram will make it easier for customers to understand what a certain setting does. I need to talk to Timm about that - the config tool is his baby, and he's the GUI expert in the company.

Yes, screenshots are needed in the documentation!

I need to install a tool that handles the pull down menus asynchronously, so that I can take screenshots from them...