Hmmm, that is because that screen is all "dynamic" using CreateImage() and CreateString() in the Program\INTERFACE\NationRelation.c script where the positions are provided by the script, not the .ini file. During those function calls, it sends a message, but the message is not sent to a "node" that knows whether the noresize value in the screen's .ini file is present, so this becomes a little trickier...I will think about a resolution for the case of CreateImage and CreateString. In the meantime, a workaround is to change the NationRelation.c script values for the sx, sz and deltaX values for the nation matrix loop that calls CreateImage and the X position value for CreateString. I will get back to you about the possibility of reverting the workaround back and have it more automatic when I find a decent solution to provide the noresize/resizeFactor for this specific situation of dynamic strings/images from the scripts vs. the .ini file.
Another solution that we used in ERAS, is this screen is marked noresize=1 in NationRelation.ini, which will stretch the entire thing back to full width, but we also added an extra country, which required more space anyway.