WA_PubScreenName not working with PPC build

I have an odd problem with the WA_PubScreenName tag, which I am using in a call to open a window using ReAction. Here is a snippet of the code:

m_poWindowObj = (Object *) WindowObject,
WA_Title, (ULONG) a_pccTitle, WINDOW_Position, WPOS_CENTERSCREEN,
WA_PubScreenName, a_pccScreenName, WA_PubScreenFallBack, TRUE,
TAG_DONE);

This code is multiplatform and can be compiled for m68k/OS3 or PPC/OS4. If I run the m68k build on OS4 then it works and the screen is opened successfully, but if I run the PPC build on OS4 then the screen is not opened, and the window opens on Workbench.

Does anyone have any ideas?

Do you have to do something different with the os4 version like ensure the public screen exists and tick the box that says auto, or something like that?

@Hitman

on OS4 check Prefs/Screens if you have such screen defined and set "Open/close automatically" check.

@Hitman,

AS the 68k version opens the screen as expected it can't be a problem with your screen database, so I would check the scopes of the variables, passing the actual screen name to the tag.

Is a_pccScreenName valid an initialised when compiled for OS4?

Add some debugprintf etc to check.

@broadblues

I finally had time to experiment with this and in order for it to work with the PPC build, I have to define a screen with the appropriate name in Prefs/Screens. And this brought back a memory of having to do this many years ago, on a different OS4 system, when I was working on this project. So that makes sense.

But what doesn't make sense, is the fact that the m68k version automatically opens this screen, even if it is not defined in Prefs/Screens! And I see no mention in the AutoDocs of automatic creation of non-defined screens. So it's a bit mysterious!

@Hitman

Quote:
Does OS3.x even have the Screens prefs editor? I thought it was an OS4 addition.