Dirka:
I went through the config files now and I see that your referencing different configuration files within the master config file. In the master config file, if it is setup for auto config, it uses the AutoConfig_ks0108-128x64_Panel.h config file. Then in the AutoConfig_ks0108-128x64_Panel.h config file, the AutoPinConfig_ks0108.h is listed again to get the pin configuration if I understand it correctly.Yes that is correct.
My question now is, can I change the AutoPinConfig_ks0108.h to PinConfig_ks0108-Uno.h in this configuration file so that the pin configuration is always set to the Arduino UNO pin configuration, even when using a Mega?
End goal is to get the existing shield working on the same pins as an UNO but only on a Mega. I hope I'm expressing myself clear enough. Let me know if I need to clarify on something and thank you again for the advice and assistance so far.
Depending on your overall needs, it might be better to use a manual config file.
This is documented in the openGLCD_config.h file but maybe it wasn't clear.
(I've updated the comments in the config file to make it clearer)
By using a manual config file you don't have to modify any of the
auto config files, and everything (panel and pin configuration) is all in one configuration file
and the pins used are the same no matter what Arduino board is used.
That is the intended way to do what you are wanting to do,
(Assuming you want the pins to be same for all board types not just Uno and Mega)
In fact, the ManualConfig_ks0108_Panel.h header file pins already match the UNO pins
so you should be able to use that manual config file "as is".
Alternatively, if you still need to keep the auto configuration capability for other boards,
you could go in an modify the pins in the Mega pin configuration file.
If you want to change the pins used in the manual configuration file,
I'd recommend making a copy of the ManualConfig_ks0108_Panel.h file (rename it for your use)
then set the GLCDCFG_GLCDCONFIG file to point to your manual configuration file
rather than editing the supplied file.
GLCDv3 Compatibility mode was intended to be used for your exact scenario
where you have an existing project and would like to move to openGLCD but due
to timing/resources there needs to be transition period where the older API interface
can still be used.
Just keep in mind that all the documentation, and many examples are documenting
and showing the openGLCD API and parameters, not the GLCDv3 API and parameters,
So you will see issues if you attempt to use sample code from the examples or
use the API functions as documented when enabling GLCDv3 compatibility mode.
It is really just intended for the transition period and not meant to be used permanently.
--- bill