开云体育

First off: I have no stake in this at all. But reading along, it seems to boil down to a UI question. And I think that sort of question has been successfully answered in other products I have used by

Crossovers can have one to four turnout actuators (and I’ve seen all combinations on real layouts) but only two actual useful states. There’s little advantage to having any additoinal turnout

The MOLE I switch machine I designed has a double ended throw side arm, so that, using tube in wire, connected at each end, it can operate throws in opposite directions simultaneously. The MOLE itself

Hi Peter: The decoder will NOT identify of I "Read type from decoder". I have not yet tried different programming modes.? I use Direct, having been warned that this is the most reliable.? I can try

Mitchell I did take a cursory glance at the fail safe, it only works after you have gone by a red light, so doesn't apply here. Steve G.

Hi I agree that the four check boxes approach aint the greatest for general use.? The generalised approach would be the Excel one of right clicking the column header and selecting the filter options,

Don, I have several on my layout. They consist of a single turnout motor driving a bar pivoted at the center point between the two switch points. (under the roadbed) Think a piece of a yardstick, but

I defy you to make a real crossover with only one turnout. Logically it may have only two states, and one JMRI "turnout" definition may suffice to control it. But, having the JMRI configuration not

Crossovers don’t require two turnouts… they really only have two usable states: “Normal” and “Diverging”. These two states can apply to multiple turnout actuators but aren’t

Bob J does a good job of focusing the problem on a key question (like he usually does!): What do we want the JMRI "LocoNet Slot Monitor" tool to do? Whatever we come up with, I think we need a

Bob, thats a great point about Multisensors generally being used with levers, and needing to be defined as getting clicked left/right or up/down. In my case, the multisensors will be disabled, as the

I agree, lots of other things in that commit. I would say the change from looking for LOCO_IN_USE to != LOCO_FREE would come closest to the older results. My other thought was if anything had a

I suspect from reading the github pages that the original intention was to offer more checkboxes to choose which things to display. So, my ideal solution would be to have checkboxes for all of the

Just a cursory look but it appears removing the right side of the && at line 182 would fix it.

That particular PR includes a lot of good stuff besides this change to the filter logic. The filter part seems to boil down to a line that says (effectively) “if no checkboxes are selected, display

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

Michael: Okay the PR3 should have enough power to program the decoder. But I've seen some BLI P3's not like the programming track, in my case on an NCE PowerCab. Need for power... the decoder doesn't

If somebody wants to look into restoring the previous behavior, the commit that changed this was You can see the full set of changes here:

I will add my vote to Dale and Ken. I do not like the change at all. I use a DCS100, so all 120 slots are 'real', but very annoying that I have to select "show all slots" to see what is there. In the

Steven, I am not a developer, but the multi sensor icon was designed to be activated by clicking it either up-down or right-left. As such, I don't believe it is possible to rotate them, say 45