Show as Window and Assume

[jholsombach]

I have a situation where i have a record format of screen fields, we'll call it rcdFields.

I have two places where i want to display these fields, one being on a tab panel and another being in a popup window.

My tab panel is in another record format. I have this format set as overlay = no, assume = no, show as window = no.

my rcdFields is set to overlay = yes, assume = yes, show as window = no.

I do a write on my tab panel record format, followed by a EXFMT on my rcdFields, followed by a read on my tab panel record format.

This works great. I see my tab panel, i see my fields, i can interact with both at same time.

Next i set up a third record format of just a regular panel, to use as the backdrop of my popup window. My fields from rcdFields should display on top of this panel.

I set my panel record format to overlay = blank, assume = blank, show as window = yes.

I do a write to my panel record format, followed by an EXFMT on my rcdFields, followed by a read on my panel record format.

This does not work. I do not see my fields. It seems like the assume on the rcdFields is not interacting with my panel window.

Are assume and show as window compatible?

What i can do, is set my panel as overlay = yes, assume = no, show as window = no.

This allows me to get my panel displayed over my existing screen and allows my fields to display on my panel, but it does not grey out the screen behind it like the Show as Window does, so it doesn't look like a true popup. Nor does it disable the screen behind the window(panel). I can still click on my grid, or click on buttons, and interact with input fields (though protect property seems to fix that).

In order to get the popup to truely work, it looks like i need to combine show as window and assume to combine my two record formats.

[David]

"assume" is compatable with "show as window" -- actually the primary usage of "assume" is to get window from stand-alone display file appearing over main screen in a different display file.

The trouble with your 2nd scenario is that writing a non-window format (rcdFields) removes all window formats.

Try setting up like this instead (and this is also simpler):

1. Put panel/dialog widget into rcdFields instead of using another record format.

2. Bind visibility property of the panel/dialog to indicator so you can hide it when not needed.

3. Bind "show as window" property of pane/dialog to same indicator so you can have window vs. non-window behavior as desired.

4. When displaying over tab panel format, turn off panel/dialog visibility and turn off show as window property using the indicator.

5. When displaying as a pop up window, use the indicator to turn on panel/dialog visibility and show as window property.

In either case, follow the same I/O steps as you are doing when displaying over the tab panel:

1. WRITE "underlying" format.

2. EXECUTE rcdFields.

3. READ "underlying" format.