There are two styles of Mcufriend Shields:
Mcufriend Red Uno Shield: 2.4" 240x320, 3.5" 320x480, 3.6" 240x400, 3.95" 320x480
Mcufriend Blue/White Uno 2.8" 240x320 shields have a 9x2 CON1 footprint for an external header.
Blue Uno Shield: 3.5" 320x480
Mcufriend Red Mega Shield: 3.5" 320x480
Blue Mega Shield: 3.2" 320x480
The library was designed for the Uno style shields. They "plug and go" on Uno, Mega, Zero, Due, Nucleo, ...
The Mega shields only mate with Mega or Due. They require USE_SPECIAL, USE_MEGA_16BIT_SHIELD
If you own a Mega, you will probably buy a Mega shield. (The Uno shield is pretty SLOW on a Mega)
You can use regular Uno shields on Uno, Zero, Nucleo, ... at the same time as Mega shield on Mega, Due.
The USE_MEGA_16BIT_SHIELD only works with Mega and Due.
There are several SPECIALs for unusual hardware. I will help you with extra SPECIALs if you verify your wiring first.
We now come to the subject of OPEN-SMART.
1. Open-Smart has different hardware wiring to Mcufriend
2. Open-Smart have never asked to use my library
3. If they asked, I would be happy to help them.
4. Open-Smart have hacked an obsolete version of my library.
5. Open-Smart examples are badly hacked.
If you enable a SPECIAL it will take preference to the regular Shield.
e.g. USE_OPENSMART_SHIELD_PINOUT will override Uno, Due, Mega but regular will work on a Nucleo.
If you want to run a Open-Smart on one Uno with a Mcufriend on a second Uno, you must build the Open-Smart with USE_SPECIAL and the regular without USE_SPECIAL.
If you want to run a Open-Smart on a Uno with a Mcufriend on a Mega, it is not beyond the wit of man to create a USE_OPENSMART_SHIELD_PINOUT_ON_UNO macro.
I either get a negative response or a sycophantic response. I get very little practical feedback e.g. suggested improvements.
What exactly do you want to do?