EventGhost

The primary purpose of this sort of event handling is to handle events that occur when you
are Not home or Not awake -- like helping to record your favorite TV show,
like millions of people purchased VCRs to perform.

As I described, I built larger Macros e.g. "Channel 1234" out of several (4 here)
smaller macros -- there is no need for an Event context to encompass multiple Macros.
Inherent in each line of the schedulghost window is, conceptually, an Event.
And here events can be triggered with respect to repetition and time, day, date.
I cannot imagine a circumstance where I would want 2 Macros to have the same name.

The concept of the Event in this program should be a module which has
inputs which trigger it (time of day etc, or from what I gather from eventghost
instructions, someone pressing a button or mouse-click)
and then that module has actions which it actuates:
those actions should be represented by Macros
which the user can build,
or Actions such as 'display a message on the pc monitor' or 'play an mp3 file', etc.

if you saw how large my tree is you would then understand, i am controlling my lights, 5 HTPC's, a network attached tv tuner, menu systems for 5 TV's the 5 tv's then selves surround sound receivers, and the list goes on and on, and i do this all from one instance of eventghost running on a server

it's very complicated

you are a single use case where the need you may not see it but there are alot of people with complicated trees.

kgschlosser wrote:if you saw how large my tree is you would then understand, i am controlling my lights, 5 HTPC's, a network attached tv tuner, menu systems for 5 TV's the 5 tv's then selves surround sound receivers, and the list goes on and on, and i do this all from one instance of eventghost running on a server
it's very complicated
you are a single use case where the need you may not see it but there are alot of people with complicated trees.

Actions triggered by time of day when the user is absent or asleep
should have the priority here.
When do you expect the schedulghost time/date scheduler to be fixed ?

Aeneas wrote:The user is forced to engage in a circuitous path to establish an Event-name
which is then assigned to the Macro-name which I have assigned
to a sequence of smaller single-digit infrared Macros I have pasted together.

Why should that Event-name be necessary in the schedulghost syntax ?
The Event-name in this particular scenario is superfluous and should be eliminated.
The Macros I have created contain the channel number infrared commands I care about
and confusing the user (and wasting the user's time) with Event-names here is unnecessary.

This is SIMPLY A BASIC PRINCIPLE EventGhost.
If not suit you, you need to find another program.
That will NEVER change.

Aeneas wrote:Are you saying that it is random whether or not the schedulghost Next Run column will display
an intent and time to perform the action/event on that line ?

No, nothing like I wrote.
I wrote (in other words), that to me it works according to (my) expectations.

Aeneas wrote:And, as I suspected, the 00:42:00 channel change event did Not occur.
Maybe there is some sort of AM bug here.

There is missing some information:
1) Provide the date and time when you create a schedule
2) Provide the date and time when the event should be generated.

Pako

I keep asking for recommendations for other programs
which can interface with the USB-UIRT and do not receive a response.
If you guys are not serious about making a working system, that is the only
endgame to this.
1) I gave this information yesterday, when the 24 hourly events were created,
creating the events using Duplicate.
2) I gave this information of the 24 hourly entries 40 minutes or 42 minutes past each hour.

If this problem has anything to do with PST time, you can set your debug PC to PST time,
then advance the time 59 minutes at a time to test each entry.
I doubt PST is related to this bug.

I keep asking for recommendations for other programs
which can interface with the USB-UIRT and do not receive a response

This forum is NOT a support center for USB-UIRT. Check with the provider of USB-UIRT for compatible software's or use Google

krambriw wrote:

I keep asking for recommendations for other programs
which can interface with the USB-UIRT and do not receive a response

This forum is NOT a support center for USB-UIRT. Check with the provider of USB-UIRT for compatible software's or use Google

USB-UIRT works, as far as I have seen --
it does not need the support of this forum.
Let me know if your group has some good news on fixing these bugs/enhancements.

Pako wrote:There is missing some information:
1) Provide the date and time when you create a schedule
2) Provide the date and time when the event should be generated.

Pako wrote:Just one example of a specific problem.
Like this:
Right now is 2016-05-08 08:00.
I create new schedule of type "Only once", that should run at 2016-05-09 07:00, but in the column Next run nothing appears.
(This is hypothetical, for me it works correctly).

Aeneas wrote:1) I gave this information yesterday, when the 24 hourly events were created,

Can you please quote your post in which the required information is included? I can not find it.

Pako

There is a message which states that at 4:30PM PST I started creating
24 hour by hour tests of this event occurring at 40 or 42 minutes past each hour.
As I have mentioned, you can set your PC temporarily to PST,
and then advance the time 59 minutes each test, in order to quickly
test this bug.

A) I suppose, we are constantly talking about the schedule of type "Only once".
I still lack information about the date. I still ask you about one thing.
1) Provide the date and time when creating a schedule.
2) Provide the date and time when the event should be triggered (and it will not happen or it will not be seen in the column Next run).
Only one single concrete. I do not need anything else.

B) Please indicate your exact time zone (offset relative to GMT)

Otherwise, I can not reproduce it.

Pako

Actually, I think I see what may be affecting this:
there is a "Choose Day" element in this window
which defaults to the current day which may be
restricting the entries to just the current day, rather than
the following 24 hours.
If on any day, I say I want the event l to occur Only Once,
at 1:40:00, that normally is understood by schedulers to mean
the next occurrence of 1:40:00, which might be into the next day.
Normally, if a scheduler refuses a time for any reason,
it will give an explicit error message (e.g. "time has past"), but this program does not.
Surprising none of you would have recognized that by now.

That still does not affect the original error in which events set for approximately 1:30AM
did not occur, until 9 hours later at 12:35:00PM.

I admire how you stubbornly continues to show,
that the mistake is somewhere else than on your side.
Besides, you do not even bother to apologize for the fact, that others needlessly robbed of time.

Aeneas wrote:If on any day, I say I want the event l to occur Only Once,
at 1:40:00, that normally is understood by schedulers to mean
the next occurrence of 1:40:00, which might be into the next day.

Only once (or yearly) means that it can be at any time.
Why should it be just the next day?
It may be, for example, for your wife's birthday, which you may have forgotten today
(that means, you will plan yesterday's date, but every year).

Aeneas wrote:Normally, if a scheduler refuses a time for any reason,
it will give an explicit error message (e.g. "time has past"), but this program does not.
Surprising none of you would have recognized that by now.

Of course, it would be possible to make such feature.
However, it is not as easy as you think.
This greatly complicates the program.
In addition, there is a checkbox Every year on the same day.
That means it would have to be also taken into account.
In this particular case, maybe I had previously programmed this function.
Maybe it would eventually cost less time than unnecessary communication with you.
This plugin there are more than 5 years, and so far nobody bothered ...

Aeneas wrote:That still does not affect the original error in which events set for approximately 1:30AM
did not occur, until 9 hours later at 12:35:00PM.

I do not understand. You can reproduce this error?
If yes, please provide all necessary information. Otherwise, I can not deal with it.

Pako

My description of what was happening was clear.
The Next Run omission from the display which I described should have been the tip off to you
that the selection was being rejected, but without an informative error message.

The program User Interface error here is that if an important choice is made in any menu which could cause
a serious failure, then the program should force the user to make that choice, Not Default the choice
to a selection which could cause errors.
Thus the "Choose day" option should be blank, until the user clicks on it, at which point
the default date could be today -- the user could then select that default actively or change to another date.

I do not think it productive to continue to debate the user interface bugs and difficulties
in this program -- you and your team either want to improve the program or you do not.
My role is simply to point out the problems.

A plugin is an addon for Event Ghost it in no way implies that any functionality of said plugin becomes the responsibility of the "EventGhost Team" a plugin is made by some standalone party and not the "EventGhost Team" and if the developer of the plugin was kind and thought others may benefit from said plugin and shares it. In no way makes the "EventGhost Team" or the devekoper responsible for maintaining or upgrading or compatability or providing support for said plugin if you had spent the time and read the top of the plugin file you would have seen this

# This file is part of EventGhost.
# Copyright (C) 2005 Lars-Peter Voss <[email protected]>
#
# EventGhost is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# EventGhost is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with EventGhost; if not, write to the Free Software
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA

Which states you don't like to read and expect and demand things to be changed to suit your needs if you have a particular need I suggest you do what every developer has done. GO AND LEARN HOW TO PROGRAM

But I see a problem with you doing that because its very apparent that you don't like to read and you will have to spend a whole lot of time doing that to learn

So there is no problem with the plugin in the first place and I was correct when I said it was a PEBKAC problem I would also like to add its an IDTENT problem as well

Problem Exists Between Keyboard And Chair
ID10T


#