ok, I still have not had a look at how much has bee done, but I can guess it is similar to what I did in 1.16.3, except that the gradient is produced as a separate binary that XaAES loads at run time. so simply speaking, you change gradients= to match the .GRD file (compiled binary)
How is the binary produced? From a C file?
My original idea was, at runtime, to be able to load and parse the actual c files as used by XaAES at compile time (to build the default gradient), but I believe it is probably outside the scope of XaAES, unless someone has a simple solution.
This sounds complex... It's been a while since I looked at the gradient stuff in XaAES, but IIRC each gradient is defined in a simple struct. So it doesn't have to be more complex than creating an external application to define the gradients, same them in a binary format and then load these in XaAES. It would be a direct replacement of the compiled-in struct.
I think Helmut has a good/working alternate solution, if XaAES is
I don't know how Helmut's solution works. But if it requires gcc and make to compile the gradients then I think it's overkill... The gradients could even be defined in a text file like the keyboard-tables, and compiled to binary format using mktbl.
Jo Even