bootblock / network-trigger Goto Github PK

Add a Ping event that opens a port and listens for a ping.

As title.

Add a BaseAction that sends a wake event to a specific or set of Mac IDs. This will allow the waking of devices when another device has been woken.

I don't personally have a use for this but others might.

Add support for allowing the blocking of wake/ping events from specific IPs.

The button next to the MAC ID textbox within the Wake Event editor needs to have its image updated and it needs to also display the list of available Devices when clicked.

The purpose of the Welcome screen is to notify the user that the application requires network access and specifically why: to detect wake broadcast messages and to perform update checking. Allow the user to disable update checking via the Welcome screen (and the Settings window, as usual).

Listening for wake on Lan messages currently requires clicking on the Listen button; this is a holdover from the initial testing implementation, so update it to the final user experience version.

Currently, when a wake event is detected the global EventCount int is incremented regardless of the destination Mac ID.

Add support for a per-Mac ID increment counter.

Having a WakeEvent that responds to a MAC ID that then performs a WakeAction sending the same MAC ID out can result in an infinite loop. There's an option within Settings - Events to prevent responding to WakeAction wake events, but add support for detecting whether an infinite loop may occur.

Add a (collapsible) panel to the bottom of the Events Monitor window that displays detailed information on the selected event.

Add options to the BaseEvent so it can optionally play back some kind of notification (sound, visual later on, etc) to denote that it has been triggered.

Add a PingAction.

Determine, and implement Edition features.

Allow the user to set an accent colour within Settings - Interface for the entire application.

The Devices which should be redesigned so now it contains a list of devices and their corresponding MAC IDs - a sort of address book.

The matched, etc, features are no longer required.

Completely redesign the application so each Action can contain multiple steps, rather than only allowing one network event to match to one Action.

While performing this re-architecture, rename the existing Action to Event and have an Action as part of an Actions collection under the Event.

Rather than just performing an equality check, perform a Regular Expression check on Device Mac IDs; this will allow block/allow lists to function as a rules-based system.

An application that reacts to wake events on the network probably shouldn't be called Ping Control, should it?

Modifying any options within the Settings window should immediately take affect; the Save button at the bottom of the window should also be removed so there's just a Close button.

All the infrastructure for WakeAction is complete except for the actual Execute() implementation.

Now that Events have their own notification settings, Action Performed can be removed. Take a pass over the other sound settings to determine whether they can be reworked or removed entirely.

As Ping and Wake events are broadcast messages, it's worth having the application itself listen for those events as one socket (each) can cover all PingEvent / WakeEvent use cases.

Ensure all forms are correctly resizable and have a MinimumSize value set.

There's an issue with cboEvent_EventSettings_PlayTriggerSound.

• Select an Event and make sure it has a trigger sound specified
• Select another Event that has no sound set
  • You need to cursor over the above ComboBoxEx control for it to correctly draw the no item selected label

The Event - History tab needs to be finished.

Complete the BaseAction.HelpText property text for all events.

By default, the Shutdown.exe notifies the user that the system will be shutting down in a minute. Add an option to disable this notice for an immediate shutdown; isn't required for the Windows API version.

Complete the BaseEvent.HelpText property text for all events.

The Event Monitor only shows events that were detected while it was open; change this so it maintains a list of events behind-the-scenes so prior events can still be shown while Event Monitor was closed.

Rather than responding to just Mac IDs, instead, create a BaseEvent that can be inherited from so multiple types of events (wake, ping, etc) can be responded to.

MAC IDs don't actually need to point to valid devices; because of this, Ping Control can match against the ID rather than EventCount to perform an action. This will allow an arbitrary number of events rather than just a count like 1, 2, 3, etc.

Rewrite the edition text for the sepEdition control in the main window.

Add an Event that'll listen for HTTP requests, specifically with specific query strings and the like.

Since the huge refactoring (see #20), the panel that displays the No Action Selected information should be rewritten as it's no longer accurate.

Allow all BaseEvents to be mass enabled/disabled via the system tray, and possibly via the main window's status bar (bottom-right).

Now that object? Data has been added to the Event Monitor, it should be displayed where appropriate within its information panel.

Network Trigger detects self-sent wake packets; this can result in an infinite loop if WakeEvent has a WakeAction.

Because of this, add an option to discard wake events that are the result of sending a wake via WakeAction.

The current use for this would be to allow the specification of something like AllowUserRun so the user can test-invoke the BaseAction via a context menu within the Actions list.

Add an optional sound to play when a device has been matched, and another sound to play when a device hasn't been matched (and thus, ignored).

Add a Category property to BaseAction so actions can be grouped rather than just all being lumped together in the Add Action drop-down.

Within the Actions tab, the Settings column needs to be populate with the configured settings for each BaseAction.

WakeEvent should be able to identify a * symbol to match all.

Allowing general wildcard matching may be implemented in the future as it doesn't entirely make sense as MAC IDs with similar values tend to be hardware of the same batch and even then they're quite different.

Also requires the actual product page to be created.

Add a toolbar to the Event Monitor containing buttons to send wake packets to the current network (using non-existent Mac IDs) so the Event Monitor can demonstrate its abilities.

Test - and implement, if required - crash handling capabilities.

Add an Interface tab to the Settings window and an option to display any detected wake events in a pop-up toast notification.

When Starting With Windows - Minimised to System Tray, the Event Monitor still appears if it was open within the previous session.

As title.

Bit of an issue fixing this one as the .NET 5 forms designer doesn't have the Tab Order feature implemented, but all controls will need their tab order corrected.

Allow BaseEvents and BaseActions (and other items, where appropriate) to be duplicated, copied and pasted.