nxevent
-
Hello,
I'd be very usefull to enhance nxevent utility for ability to send event by using event's name (instead of event_id code).
Another not so important notes:
-
nxevent command should exit with non zero return code if sending of event was not successfull.
-
implementation of any kind of persistence (e.g. buffering of events at the sender's side) is welcomed for event sending utility to overcome situations like: short lasting server unavailability or broken network communication
note: nxevent -w parameter seems it is not applied for this use case
And thanks for nice software.
Kind Regards,
Roman -
-
Hi!
I've implemented #1 and #2 (event identification by name and correct return codes). #3 is a bit more complicated so I'll do it later
Best regards,
Victor -
Hi,
Thank you for quick reply
During testing I've found following behaviour which I suppose is not correct:
During import of configuration (e.g. events), user events (id > 100000) are not correctly replaced in the case event name and/or event id already exist. Events are always appended as new ones (with new id) regardless any checkbox is selected. Also more events can have the same name as uniqueness of name is not checked (there is no constrain).
tested on 1.2.14, windows version
Kind Regards,
Roman
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login