¿ªÔÆÌåÓý

Locked Re: possible bug, LocoNet slot monitor


 

I think this should be reverted before the release of 4.15. If I could convince myself to participate in the development of this product I would do it but I've been retired for just 1 year and need to get away from Java for a while (java engineer for many years).?


On Wed, Nov 28, 2018 at 12:08 AM Bob Jacobsen <rgj1927@...> wrote:
If somebody wants to look into restoring the previous behavior, the commit that changed this was

> commit 7cc228bfaf451520ea16cb8e18b950050d1f9a4d
> Date:? ?Tue Dec 19 19:59:16 2017 -0500
>
>? ? ?Partly add filtering to Slot Monitor table
>? ? ?
>? ? ?Need to use filtering instead of manipulating the model to implement checkboxes showing/hiding certain types of slots.
>
> :040000 040000 e4378d76dab518e516a5ef33130d95bdfc1db7d0 d8cfda18046228b646c8ead203ceabd08b7bf201 M? ? java

You can see the full set of changes here:?

The PR that included it is here:?
It¡¯s called "Fix errors reading slots in Slot Monitor¡±

It doesn¡¯t look to me like the Zephyr behavior change was intended, but rather an unintended part of fixing some intermittent failures under load.

It first appeared in JMRI 4.11.1 on December 24th, 2017.

Bob
--
Bob Jacobsen
rgj1927@...








--
John Griffin? ? ? ? ? ? ? ? ?
_______________________________
If today was your last day, you would...

Join [email protected] to automatically receive all group messages.