akbyrd / lcdhardwaremonitor Goto Github PK

Essentially a 'saved selection set'. Picking a group or a layer selects all the elements in that group or layer.

Should be able to set how often the sources, widgets, and/or LCD updates

Ideas:

• Global update rate for the application. e.g. sources and screen are updated 10x a second
• Independent update rates for sources. Some may be heavier to check than others
• Independent update rates for widgets. Some things probably don't need to be updated as frequently. This could be set either directly or as a multiple of the global update rate

i.e. Top Left, Top, Top Right, etc
Default to Center

• Selecting a widget should show it's settings (and the widget settings)
• Selecting multiple widgets should show the most derived settings type they all share

See App.xaml.cs in the Prism 5.0 StockTrader example for an example.

Would it be possible to display a Rainmeter skin as-is on the LCD? If they expose/are willing to expose a texture or D3D surface, it should be pretty easy.

• Arrow keys to move (modified keys to move in large steps)
• Delete to remove the widget

Starting up OHM takes a few seconds. Should load application, show spinner while loading drawables from file, then show spinner on sensors if shown before OHM is done loading. If OHM isn't loaded on another thread, show a spinner on the main window before loading any layouts.

• Right-click a sensor in any source list and hide it
• Hidden sensors are collapsed under a parent item in lists
• Right clicking a hidden sensors shows "Unhide"
• Right-clicking the parent shows "Unhide all"

Potential widgets:

• Who is speaking
• Mute/deafen state
• Current room

Potential widgets:

• Who is speaking
• Mute/deafen state
• Current room

Potential widgets:

• Who is speaking
• Mute/deafen state
• Current room

Name
Settings (data source, draw order, size, colors, labels, positions, borders, font, pivot)
Drag and drop to place

• When a widget is selected, the drawables list should disappear and the sensor list should take it's place.
• Dragging and dropping a sensor onto a widget should assign that sensor

When triggering an animation while one is already in progress, no animation is played (e.g. click between pages quickly).

Styles contain a set of common properties such as color, font, text size, etc. Multiple styles will be able to be on each element. The styles will apply in a specified order with subsequent styles simply overwriting values from previous styles. This will allow a great way to create 'themes' and change multiple elements at once.

Potentially show a 'final style' preview where the final resulting values after combining multiple styles is shown. This could just be a few text fields following or preceding the style list.

The D3D example uses a 'dllmain.cpp' and module definition file to export the interface, but the VS project auto-generated a file using a fancy macro and __declspec(dllexport). Seems like the second approach is cleaner. Already have to replicate the interface on the native side, don't want to have in a third place with the module def.

It should be possible for other people to compile visuals to be displayed on the LCD into a DLL. Those DLLs should be able to be shared and placed in a folder and loaded at runtime. There should be a way to force reloading of these while the application is running, for convenience.

e.g. In Sources/OHM

Should be able to assign a named color (e.g. Dark Red) to an element. If the named color changes, all elements using it should automatically change as well. Named colors will probably be edited on another page.

When right clicking near the top of the window, the normal context menu containing Move, Size, Minimize, Close, etc shows up. Get rid of it. Probably requires WinAPI.

http://www.codeproject.com/Tips/320885/Customize-Window-System-Menu-in-WPF

Should be able to highlight multiple displayable elements and move them together.

Multi-select should be possible by ctrl-clicking multiple items or dragging a selection rectangle.