HC_Set_Window_With_Options

void HC_Set_Window_With_Options(double left, double right, double bottom, double top, char const *options)
void HC_Set_Window_With_Options(double left, double right, double bottom, double top, char const options)

Limits the amount of the screen (or the containing Window) to be used by the referenced segment upon display.

Windows are used to allocate chunks of the screen to different scenes or information. The portion of the user data space specified by the Camera positioning, or camera volume, is symmetrically scaled to fit into the requested area.

Functions such as Set_Camera_By_Volume() select how much of the data space should be directed to the screen; Set_Window() defines where on the screen that picture should land. The loose ends of the picture which may extend out beyond the edge of the Window after all the transforming is done are clipped off.

Windows are cumulative - the window highest in your segment tree is allocated from the entire screen. Each segment, going down the segment tree, which specifies a Window, takes its size with respect to the containing segment’s Window.

Windows are normally opaque and cover up the scene underneath, but transparent windows are available via a “clear” window pattern. See Set_Window_Pattern() .

Set_Window_With_Options extends Set_Window with some new capabilities, via the options argument.

  • offsets = (left_offset, right_offset, bottom_offset, top_offset) The normal window limits are fractional portions of the parent window. Offsets are pixel adjustments in addition to that, allowing for more flexibility without having to recompute the limits when things like the containing GUI window change size. The normal left<right and bottom<top restrictions are not enforced as it is often useful to have them equal. For example limits and offsets of (-1,-1,1,1)[0,50,-50,0] describe a subwindow where every part is defined from the top left corner of the parent, but the bottom and right moved 50 pixels in the appropriate direction a 50x50 box stuck in the upper-left corner.
  • [no] subwindow sorting [= on | off] Subwindows are normally drawn in the order they are visited in the tree walk (after any non-windowed items). Turning on this option indicates that any contained subwindows are to be drawn in order of their segment priority, (lowest values first, see Set_Priority() ). In the case of matching priorities, any Z value due to using a Set_Window_By_Point will be used as a secondary sort. This means you can have multiple “label” subwindows, all set with the same priority (say 0) and they can follow the underlying geometry, but you can set a higher priority to temporarily pop one [or more] on top to highlight, and reset the priority to restore the z-sort behavior.

Bring_To_Front() is called automatically for any newly-windowed segment. If there are any conflicts between sibling windows (windows side-by-side in the segment tree), the most recently-created windows are forced to be uppermost on the screen. Further calls to Bring_To_Front() or Set_Priority() might be necessary to get the ordering you want. Note that a subwindow, as opposed to a sibling window, is always “in front of” its containing window. Also, if sibling windows do not actually overlap their ordering shouldn’t matter.

If HOOPS is actually running within another windowing system (such as X or UIS), then the top-level window controls the size of the master window that HOOPS requests from the containing windowing system, subject to any “subscreen” Driver Option.

It is permissible for a Window’s coordinates to appear to exceed the boundaries of its parent window. i.e., it is legal to provide window coordinates outside the range -1 to +1. The scene and the subwindows are fitted into the oversize window as if it really were the specified size. However, the oversize window will be clipped off at the edge of the parent window. It is not really possible to exceed the parent - there are numerous code optimizations that depend on this. “Oversize” windows sometimes make window calculations simpler.

If a window is set directly on the “?picture” segment, then selection-testing and window-manager resizing become confused. HOOPS window behavior is technically undefined if a window is set at a driver level segment such as “?picture”. Applications should rely on the default window (-1.0, 1.0, -1.0, 1.0) already present at the driver level or use the “subscreen” driver option to manipulate this default window.

HC_Set_Color, HC_Set_Window_Pattern, HC_Set_Window_Frame, HC_Bring_To_Front, HC_Set_Priority(), HC_Set_Driver_Options.

Parameters

left: Minimum limit, along the horizontal axis of the screen. The leftmost edge is at -1.

right: Maximum limit, along the horizontal axis of the screen. The rightmost edge is at +1.

bottom: Minimum limit, along the vertical axis of the screen. The lowest possible position is at -1.

top: Maximum limit, along the vertical axis of the screen. The highest possible position is at +1.

options: A quoted string or a string variable containing a list of the desired settings.