Page 10 of 10 FirstFirst ... 58910
Results 136 to 141 of 141

Thread: StatusDisplay - status.json / journal display and surface navigation assistant.

  1. #136
    Originally Posted by Robert Maynard View Post (Source)
    There is (at the moment, that may change or be optional). If no positional information is available it will hide itself. If no destination is set then the elements relating to the destination will not be displayed (but CoG and SoG will remain, while positional information is available).
    Okay, that explains why I don't see it, I'll give it a try next time I'm home. I would think this isn't really something I'd want on an auxiliary monitor although I'm wondering how well it will work with TrackIR.

    Thanks.

  2. #137
    Beta 0.0.4.1 released. Download link: https://cdn.discordapp.com/attachmen...180828-1726.7z

    Change log:

    1) Added /Publish and /ReadHere command line parameters to instruct StatusDisplay to write journal / status.json data as it comes in to the same directory that the executable is in and to read from that directory. Only one can be selected. Requires two copies of StatusDisplay to be running to function. Allows game information to be able to be displayed on a different PC.

    To do list:

    1) Add waypoint count to Tiny display and re-order Tiny elements for easier / quicker reading.
    2) Add inter-system route handling.
    3) Improve parsing coverage of possible events listed in the Journal documentation.
    4) Add defined buttons to display information read from the Journal.
    5) Improve defined button display based on status.json information.

  3. #138
    Teaser for next Beta release: new "Panel" window.



    This is a user-configurable display of (up to) 144 elements, arranged in a 12 x 12 grid. Each element can be set to be either "null" or to one of the existing nine panels (i.e. Posn, Dest, Jrnl, Comms, Info, Time, Flags, Location or Trip). Assigned elements of the same type are automatically merged into "chunks", firstly horizontally and then vertically. The image above represents three set elements only and is 1200px x 105px - "null" elements are not drawn unless required (i.e. in "gaps" in the assigned elements). The window can be resized in the range 240px x 100px to 3840px x2160px.

    [edit 1] After a bit more work, it seems that this approach could be used in the main overlay window, e.g.


    The current overlay is on the left. The right hand image is a panel of 8 assigned elements in one column.

    More thought required.

    [edit 2] Having thought about it a bit more, I am inclined to replace the current main overlay with a panel. Then there's the fact that the centre of each MFD is a 4 x 5 grid that could also benefit from (optional) "chunk" merging by adding the panels to the list of available button options, removing the current checkboxes for panels and adding a checkbox for chunk merging.

    [edit 3] After some significant refactoring, the next Beta will have four "Panel" displays (the existing Main Overlay; the TinyDest display and two new panels) and four MFD displays.

  4. #139
    Beta 0.0.4.2 released. Download link: https://cdn.discordapp.com/attachmen...180924-2057.7z

    Change log:

    1) Under the hood: move from fixed size (rolling) arrays for particular data to C++ vectors.
    2) Refactoring and consolidation of data structures.
    3) New approach to "Panel" displays - a 12x12 grid of elements can be set to any of the available panels (or blank) and they will be auto-merged into larger chunks if adjacent and will form a rectangle. Panel size can be set in the range 240px x 40px to 3840px x 2160px.
    4) Main overlay and tiny displays converted into panels. Two more panels added (P#0 and P#1). Tiny panel "hides" when GUI mode is other than "looking out" of the cockpit.
    5) Existing Tiny display elements are now microPanels (designated with "m" prepended to the panel name). Lap / waypoint count added.

    Known issues:

    1) Border of main panel cannot be toggled therefore main panel size must be set using new panel settings dialog.
    2) Main panel may not immediately resize using dialog - workaround is to toggle the border of the main panel (I'm not sure why this works but I'll take it....).
    3) The settings dialogs may at times become unresponsive. If this happens, activate a panel or MFD display (by clicking on it with the mouse) and then LEFT ALT-Q to quit.

    To do list:

    1) Add inter-system route handling.
    2) Improve parsing coverage of possible events listed in the Journal documentation.
    3) Add defined buttons to display information read from the Journal.
    4) Improve defined button display based on status.json information.

  5. #140
    Beta 0.0.4.3 released. Download link: https://cdn.discordapp.com/attachmen...181005-1922.7z

    Change log:

    1) Added a few new micro-Panels.
    2) Tweaked the raw flags panel, now shows two-letter designation for flags.

    Known issues:

    1) Border of main panel cannot be toggled therefore main panel size must be set using new panel settings dialog.
    2) Main panel may not immediately resize using dialog - workaround is to toggle the border of the main panel (I'm not sure why this works but I'll take it....).
    3) The settings dialogs may at times become unresponsive. If this happens, activate a panel or MFD display (by clicking on it with the mouse) and then LEFT ALT-Q to quit.

    To do list:

    1) Add inter-system route handling.
    2) Improve parsing coverage of possible events listed in the Journal documentation.
    3) Add defined buttons to display information read from the Journal.
    4) Improve defined button display based on status.json information.[/QUOTE]

  6. #141
    Beta 0.0.4.4 released. Download link: https://cdn.discordapp.com/attachmen...181006-1449.7z

    Change log:

    1) Fixed bug in parsing of GuiFocus and FireGroup from status.json.
    2) Fixed bug in Tiny panel hiding when GuiFocus <> 0, i.e. not the straight ahead view out of the cockpit (it wasn't).
    3) Fixed bug in Options panel that prevented both enabling and disabling Tiny panel.

    Known issues:

    1) Border of main panel cannot be toggled therefore main panel size must be set using new panel settings dialog.
    2) Main panel may not immediately resize using dialog - workaround is to toggle the border of the main panel (I'm not sure why this works but I'll take it....).
    3) The settings dialogs may at times become unresponsive. If this happens, activate a panel or MFD display (by clicking on it with the mouse) and then LEFT ALT-Q to quit.

    To do list:

    1) Add inter-system route handling.
    2) Improve parsing coverage of possible events listed in the Journal documentation.
    3) Add defined buttons to display information read from the Journal.
    4) Improve defined button display based on status.json information.[/QUOTE][/QUOTE]

Page 10 of 10 FirstFirst ... 58910