<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Steve,<br>
<br>
<div class="moz-cite-prefix">Am 04.01.21 um 08:32 schrieb Stephen
Casner:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.OSX.2.21.9999.2101032326300.41306@auge.attlocal.net">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">technically may send "*" as an event, it isn't meant to be used that way, just
gets added to the map because of the "any event" listeners.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I see. If raising event "*" should be avoided, though, the
event_raise() function should check for that.</pre>
</blockquote>
<br>
That's an option for later, but not actually necessary, as it does
no harm. But if users see "*" in the suggestions (!) of the command,
they will interpret that as a defined feature.<br>
<br>
<blockquote type="cite"
cite="mid:alpine.OSX.2.21.9999.2101032326300.41306@auge.attlocal.net">
<pre class="moz-quote-pre" wrap="">For someone writing new code who wants to listen for an event but does
not know exactly how the event is written, the answer is not easy to
find. I added "event list" to help with that, but based on what you
say here that's not really valid or complete, either.
</pre>
</blockquote>
<br>
"event list" has been more of an internal system/debug utility for
me, and it does exactly what it's description says, so that's
totally valid for me. Events should stay light weight, as in
Javascript. Adding a registry for all possible event names would add
a lot of complexity without much benefit. For example, the location
framework would need to take care to deregister events for deleted
or renamed locations etc.<br>
<br>
For someone new to the event system, this is the place to start and
the reference for defined standard framework events:<br>
<ul>
<li><a class="moz-txt-link-freetext" href="https://docs.openvehicles.com/en/latest/userguide/events.html">https://docs.openvehicles.com/en/latest/userguide/events.html</a></li>
</ul>
Framework events added by vehicles shall be documented on the
respective vehicle page, e.g.:<br>
<ul>
<li><a class="moz-txt-link-freetext" href="https://docs.openvehicles.com/en/latest/components/vehicle_renaulttwizy/docs/events.html">https://docs.openvehicles.com/en/latest/components/vehicle_renaulttwizy/docs/events.html</a></li>
</ul>
And custom events added by plugins shall be documented on the
respective plugin page, e.g.:<br>
<ul>
<li><a class="moz-txt-link-freetext" href="https://docs.openvehicles.com/en/latest/plugin/edimax/README.html#events">https://docs.openvehicles.com/en/latest/plugin/edimax/README.html#events</a><br>
</li>
</ul>
<br>
Regards,<br>
Michael<br>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
</body>
</html>