¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. OccultWatcher
  2. Topics

Suggestion for a new feature

 

I would like the ability to flag events as (forget about it), such as making the little icon to the left of each event something that would tell me that there is no reason to consider this event (distance, etc).?
Perhaps a new menu item on the right-click menu that says "Ignore".
That way, we don't have to remember if we already checked out an event for consideration.
Of course we would still be able to change our mind by adding the event to our "my events" list.

This one would take a little work (GUI and data structure), but for me it would useful.

If there already a way to do this, I haven't figured it out yet.

VS
 


Seconded. This feature would be very useful.

I often find myself looking through my feed and thinking...
"Have I looked at this event before? Why didn't I add it my events? Oh, it's too low!"
So time is wasted assessing events multiple times.

Peter N
 

There is one thing you can do now, it is to select the event and press the 'Del' button to hide the event.

You cannot unhide a single event, but you can unhide all hidden events if you press Ctrl + Shift + Z

The other option is to update your filters. There are already filters on altitude and rank for example. What type of events you would like to hide/ignroe and why those events have made it to your list?

I'm guessing this is because you didn't want to miss and exceptional event with sub-optimal altiture. If this is your case then pessing 'Del' will probably be a good option for you. Otherwise let me know how I could improve the filers.

Also does anyone have experience with C# and is willing to contribute to the development of OccultWatcher? l'll take help every day.

Cheers,
Hristo.


On Thursday, August 5, 2021, 8:28:18 AM GMT+10, Peter Nosworthy <yahoo@...> wrote:



Seconded. This feature would be very useful.

I often find myself looking through my feed and thinking...
"Have I looked at this event before? Why didn't I add it my events? Oh, it's too low!"
So time is wasted assessing events multiple times.

Peter N

 

Hristo,

Thanks for the tip about the Del and unhide events keys.

I just knew you were going to ask about filters! LOL

I keep my magnitude limit a little higher than what I can probably see with my scope. sometimes the star is redder than indicated and it shows up on the camera so I try to do a dry run of those events in advance to see if I can actually image it. It also gives me the opportunity to integrate, if necessary, but that also depends on the duration. I expand my radius wider than I would normally travel just in case there is a "special" event that i should consider.? The bottom line is, I might have many potential events on my list that I won't end up observing but I don't want to risk missing an event just because I had a filter value set too conservatively.?

Ok, i tried the "DEL" key and that works. and the "unhide" worked as well.? Question about "unhide", though. If I deleted an entry last month would it appear again, or is the unhide based on the retention (keep showing...) limit?? I hope the latter. But? how about a counter compromise. If an event ages (happened yesterday), you still show it on the list, with dimmed text. Why not do the same for deleted events. still show them, but as dimmed. users can tell the difference between the two because one will have an old date and the other in the future. eventually the deleted one will disappear once the retention date has passed.
I could live with that!

vince
 


Thanks Hristo. The hide feature seems to work well.

Regarding filters, I have my filters set to show many more events than I actuially observe. Here's an example of why...

If there's a difficult event (low altitude, dim target, low probability, low mag drop etc.) at 4am I would normally reject it because it's a lot of effort which will probably be wasted.
However, if there's also an easy event 20 minutes before the difficult one, then I'll probably attempt both, as I'll already be awake and have all my equipment running. So it's not much extra effort to observe the difficult event.

That's why I don't filter out those difficult ones, but only reject them after looking at them in the context of the other events in my feed.

Peter Nosworthy

1 - 5 of 5