-
Walt, Agree with you on that one, I have made the change and will commit it later on today.
2009-11-06 10:48:21 UTC in JMRI Model Railroad Interface
-
The fix has been committed to CVS, and will be in the next release.
2009-11-05 18:02:46 UTC in JMRI Model Railroad Interface
-
This is now resolved and the fix committed.
2009-11-05 18:02:46 UTC in JMRI Model Railroad Interface
-
I have been able to resolve the first issue with the text field. I'm not 100% sure about the turnout as they are displayed differently to the sensors/signals etc.
2009-11-05 18:01:45 UTC in JMRI Model Railroad Interface
-
I have found the issue, and shall commit the fix as soon as i can.
2009-11-04 11:52:59 UTC in JMRI Model Railroad Interface
-
I have had a brief initial look into this. it is certainly an issue is 2.6.1, and it also affects the multisensor. It appears as if the x,y, co-ordinates are not translated for a clicked on item when zoomed in, however the show pop up works.
2009-11-04 10:48:42 UTC in JMRI Model Railroad Interface
-
Item 2 - Shouldn't be too difficult to add a blank line to force the user to select the correct type of signal head.
Item 3 - I'll sort out as it was my fault for putting the signals in alphabetically order, rather than all jumbled up.
2009-10-26 15:26:31 UTC in JMRI Model Railroad Interface
-
I'm going through merging code between certain elements of the layout editor and the panel editor, this issue might get resolved with this.
2009-10-26 15:20:16 UTC in JMRI Model Railroad Interface
-
Attached is an update to the Ecos that now provides a throttle function. Due to the nature of the ecos I have had to create a new Ecoslocoaddress class and manager that simply holds the dcc address to the ecos object id hence the update to the instancemanger.java file.
If a loco isn't already registered on the ecos, a new object is created on the ecos and registered, the process of creating...
2009-07-08 22:58:19 UTC in JMRI Model Railroad Interface
-
Within File DefaultLogixManager.java, we have the class activateAllLogixs()
From there you have the lines
if(loadDisabled){
x.setEnabled(false);
}
x.activateLogix()
Given that we have set the logix to be disabled, we are then going ahead and running the activateLogix() command.
I therefore suggest that this is changed to
if(loadDisabled){
x.setEnabled(false);
}
if...
2009-07-06 17:16:54 UTC in JMRI Model Railroad Interface
