Layouteditor user group series#

It doesn't reference LayoutBlock objects. It is stored at the user level ('Store Panels.')Ī BlockValueFile stores and loads the value (internal temporary contents) of Block LayoutEditorXml handles the storing and loading of all the track and icon objects. They are stored with the configuration information because they can be used LayoutBlockManager is stored and loaded in the usual manager way, including the LayoutBlock objects. Only LayoutBlockManager and LayoutEditor are registered with the ConfigureManager. LayoutEditor (registered with ConfigurationManager).LayoutBlockManager (registered with ConfigurationManager).The classes that have ConfigureXML partner classes are: Swing components and AWT-style paint operations. The goal is a MVC-like structure, with modifications to account for the mix of Loop through a list from LayoutEditor.getLayoutTracks()Ĭalling their individual LayoutTrackView.draw1(2D, boolean, boolean) and LayoutTrackView.draw1(2D, boolean, boolean) Or LayoutEditorComponent.draw2(2D, boolean, float). Off by a call to LayoutEditor.redrawPanel().Įach of those layer private methods sets up graphics and method options, thenĬalls LayoutEditorComponent.draw1(2D, boolean, boolean, boolean) That in turn is invoked via the usual repaint() mechanism, although it's often kicked

Layouteditor user group series#

That invokes a series of internal private methods to display the layers of the layout drawing. LayoutEditorComponent isĪ JComponent with a LayoutEditorComponent.paint() public method The LayoutTrackView tree defines draw1 and draw2 methods thatĭraw two different representations of the track elements. The Layout Editor window consists of a menu bar and an upper tool-bar that are all made with The LayoutBlock class is at the heart of the navigation web for layout-representing objects.

Three subpackages provide specific services:.Sounds like a base class for others, it's not it's part of the LayoutEditor implementation.) MultiIconEditor, and MultiSensorIconFrame, extend Swing or AWT components. Multiple classes, including LayoutEditorAction, LayoutEditorComponent, LayoutEditorToolBarPanel,.BlockContentsIcon, MemoryIcon inherit from the equivalents in the package.

With a Block which it created the Block has a specific form for its system name and the LayoutBlock's name as its user-name. If present, the sensorĭefines occupancy for the LayoutBlock. Of track segments and turnouts that corresponds to a 'block'.

LayoutBlock and LayoutBlockManager are a NamedBean pair.

New classes are being added to represent the specific types previously implemented via type variables and conditional code.

The track is represented by a hierarchy of classes that's rooted in LayoutTrack and completely disconnected from.

Turnouts also have a type variable to represent their geometry, i.e. Its type variable, and that can be queried by following the link as there's only one connection to a PositionablePoint. There's no type1 value representing the far end of the connection from the EB and EC either.īut the EB and EC PositionablePoint knows what itself is through Specifically a END BUMPER or EDGE CONNECTOR. The far end sees the connection to the EB and EC as to a POS_POINT, not This is coded and stored as the following: (Some graphical attributes removed, reordered)įor TrackSegment objects, a connection is represented by the name of the other end, and the type (in type2 or type2) of the connection at the other end.įor example, a connection in object T1 to a turnout might give the turnouts TO1 name, and that the connection is to the TURNOUT_C leg of that turnout.Ĭonnections to END BUMPERs and EDGE CONNECTORs don't quite fit that. Work is proceeding to separate those out and provide clean interfaces for other packages to access the structural information. Layout Editor currently represents both structure and graphical display through a single set of objects.