Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A more detailed description of drag and drop functionality is given below, but the following videos will introduce you to the basic concepts:



Panel
bgColor#e6f0ff
titleBGColor#99c2ff
titleTechnical Breakout

If a single read brings back a number of records exceeding 90% of the specified cache size, a warning message will be logged to the console.

If a single read brings back 100% or more of the cache size, and the enforce cache size limit flag is ticked in the system configuration, then the analysis run will stop completely.

Code Block
titleError Message: Cache Size Limit Exceeded
The Pipe "stream_name.lookup_pipe_name" cache is 100% full (the cache size is 10).

A model administrator can use this information to make an informed decision about the design of the model.




Pinning and unpinning

A key concept behind dragging functionality in forms is pinning and unpinning. 

Unpinned components

Unpinned components  Unpinned components are placed into the next available space. Pinned components can be placed anywhere on the form, and you can pin the edges to the edges of the parent components component by setting the offset offsets between the top, right, bottom and left edges of the component to those of the parent.

...

Unpinned components

This is done using the Positional Settings of the component. The offsets are set as the number of pixels.

Note that if you set the right Positional Settings, this overrides any width set for the component. Similarly, if you set the bottom Positional Settings, this overrides any height set.

Note

control which is next available space using CSS?

Unpinned components are a good idea if your layout is likely to be presented on a variety of different screens of different sizes since the components will simply flow to fit the available screen space.  Pinned components cannot do this and may end up being drawn off the screen resulting in scroll bars (if they are enabled on the parent area) or simply not being visibleUnpinned components are placed automatically in the next space available.


By default this is underneath the previous component - but this can be controlled in CSS. A full discussion of the CSS options for controlling this are beyond the scope of this article, but can be researched on the web. If you want to do this, note that components in forms are represents as DIV objects. Future versions of PhixFlow will features easy to use options to control which space components will flow into.



(Notes for pop out hints box: To control which components are drawn on top of which you can add a zIndex css tag in the ‘CSS Properties’ sections of the relevant components.  The value of the zIndex tag should be a number and components are drawn on top of each other in ascending sequence of zIndex numbers.)

Pinned components

This is done using the Positional Settings of the component. The offsets are set as the number of pixels.

Note that if you set the right Positional Settings, this overrides any width set for the component. Similarly, if you set the bottom Positional Settings, this overrides any height set.

Note

control which is next available space using CSS?





Dropping components onto forms to create content

...