jmri-developers — Discussion of current and future development.

[Jmri-developers] Cannot build after a merge from master

[Cressman <pgc...@sb...>]

Before submitting a pull request I did a merge into the branch while I had the version of PanelPro running.  Yes, a mistake I didn't notice.  The merge failed and so I repeated it with another merge that reports everything up to date.  However, after these merges from git master I get these compile errors for a clean build:       [javac] C:\Git\JMRI\java\src\jmri\web\servlet\panel\ControlPanelServlet.java:66: error: cannot find symbol
       [javac]                         panel.addContent(positionableElement(sub));
       [javac]                                          ^
       [javac]   symbol:   method positionableElement(Positionable)
       [javac]   location: class ControlPanelServlet
       [javac] C:\Git\JMRI\java\src\jmri\web\servlet\panel\LayoutPanelServlet.java:80: error: cannot find symbol
       [javac]                         panel.addContent(positionableElement(sub));
       [javac]                                          ^
       [javac]   symbol:   method positionableElement(Positionable)
       [javac]   location: class LayoutPanelServlet

Hoping that whatever corrupted the branch would not be pushed to Git, I committed, pushed and requested a pull.  The same compile errors occur on Git hub.  Locally, I copied in 2 files from my local master that resolve the missing positionableElement() method.  However, this then leads to other compile errors for references these replacements need. I hesitate to continue overwriting files from my local master.  BTW merging to my local master was successful and clean builds can be done.

Using the "Replace with Head Reversion" of Eclipse does not fix the problem.  I don't understand the 'git rebase' or 'git revert' commands well enough to use them.  I'd like some advice before I screw up the branch even further.  I need to undo the merge on my local branch, not the commit on my fork at git hub  (although that would be OKto do).  The important thing is not to lose all the work I did locally before the merge to the branch.
Any advice would be most welcome.PeteC

Re: [Jmri-developers] Migration of this list to Groups.io - proposal

[Matthew H. <mat...@gm...>]

Dear all,

This list on SourceForge has now been placed in read-only mode - to
continue to participate in JMRI developer discussion, please see the new
list at https://jmri-developers.groups.io/g/jmri

Best regards,

Matt H

On Thu, 6 Dec 2018 at 11:47, Matthew Harris <mat...@gm...>
wrote:

> Dear all,
>
> Given that there has been a flurry of activity on this list, we will wait
> for that to calm down before placing this list in read-only mode.
>
> As a reminder, it is necessary for anyone wishing to follow/participate in
> JMRI developer discussion to manually subscribe to the new list via web at
> https://jmri-developers.groups.io/g/jmri/join or emailing
> jmr...@jm...
>
> This is due to SF no longer allowing us to access or export the subscriber
> list.
>
> Current plan is to switch THIS list (on SourceForge) to read-only mode
> some time around 20h00 UTC today (6th December).
>
> After that time, conversations should take place on the groups.io list.
>
> The list archive will remain here, but we will organise an import of the
> archive to groups.io in the meantime.
>
> Best regards,
>
> Matt H
>
>
> On Fri, 30 Nov 2018 at 23:44, Bob Jacobsen via Jmri-developers <
> jmr...@li...> wrote:
>
>> First, I’d like to thank Matt for thinking all this through.
>>
>> This sounds like a plan that we should implement sooner rather than
>> later.
>>
>> Bob
>>
>> > On Nov 29, 2018, at 1:32 AM, Matthew Harris <
>> mat...@gm...> wrote:
>> >
>> > Dear all,
>> >
>> > As some of you may recall, over the last few years, we've been
>> experiencing several issues with various aspects of the SourceForge
>> infrastructure which has resulted in us migrating the majority of our
>> development tool set away to other alternatives.
>> >
>> > Today, the last parts of the JMRI development tool set that still rely
>> on SourceForge are a few of our mailing lists, mainly this one and the
>> 'jmri-announce' list.
>> >
>> > Several months ago, due to reliability issues noticed with the Yahoo!
>> platform, we migrated the 'jmriusers' group from Yahoo! Groups to Groups.io.
>> >
>> > Around that same time, we also created a 'shadow' developers list on
>> Groups.io, which was configured to receive copies of all messages posted
>> here so as to already start building up an archive of recent activity.
>> >
>> > Our experience thus far with 'jmriusers' on Groups.io has been positive
>> so the time has now come to switch over fully to Groups.io for these last
>> remaining lists.
>> >
>> > Unfortunately, due to restrictions of the SourceForge platform, it's
>> not possible for us to retrieve a list of subscribers to the various JMRI
>> mailing lists, meaning that it will be necessary to manually subscribe
>> yourself to the new list on Groups.io.
>> >
>> > As a result, there will need to be a cut over period during which
>> conversations might end up happening on both lists (this has already
>> happened in a few cases) so we need to define a suitable timeline for the
>> cut over.
>> >
>> > My proposal for the cut over is as follows:
>> >
>> > - Encourage new sign-ups to the new jmri-developers list via web at
>> https://jmri-developers.groups.io/g/jmri or by email via
>> jmr...@jm...
>> > - Place this list into read-only mode after a grace period (say 1 week)
>> to minimise risk of conversations in both places
>> > - (Optionally) transfer archive of messages from this list
>> >
>> > Thanks to Bob, we've got a pretty much complete archive of the messages
>> from this list in a suitable format so it shouldn't be too much effort to
>> get this imported into Groups.io. Given that we've already been building up
>> an archive, we might end up with some duplicated messages and some out of
>> order, but I'd suggest that's more of an inconvenience than anything else.
>> >
>> > The new list is configured as a main list (
>> jm...@jm...) with sub-groups for specific purposes,
>> such as commit messages and infrastructure monitoring, to which you are
>> able to optionally subscribe.
>> >
>> > Please let me know any comments/remarks regarding this proposal so we
>> can determine the best route forward.
>> >
>> > Best regards,
>> >
>> > Matt H
>> > _______________________________________________
>> > Jmri-developers mailing list
>> > Jmr...@li...
>> > https://lists.sourceforge.net/lists/listinfo/jmri-developers
>>
>> --
>> Bob Jacobsen
>> jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
>>
>>
>>
>> _______________________________________________
>> Jmri-developers mailing list
>> Jmr...@li...
>> https://lists.sourceforge.net/lists/listinfo/jmri-developers
>>
>

Re: [Jmri-developers] First 4.13.6 files available

[Balazs R. <bal...@gm...>]

Seems to work fine for OpenLCB stuff.

I found a bunch of ConcurrentModificationExceptions when deleting sensors
from the sensor table. Filed https://github.com/JMRI/JMRI/issues/6254 to
track it.


On Thu, Dec 6, 2018 at 4:59 PM Klaus Killinger <kla...@t-...>
wrote:

> Yes, it used to work for me pre-4.13.6. I have a local repository
> 4.13.6ish (I think it is from 21 November 2018) where it works.
>
> I have to switch the Preferences >> Defaults from "Z21" to "Internal".
>
> Klaus
>
>
> Am 06.12.2018 um 11:29 schrieb Bob Jacobsen via Jmri-developers:
> >
> >
> >> On Dec 6, 2018, at 12:48 AM, Klaus Killinger <
> kla...@t-...> wrote:
> >>
> >> Windows 7, PanelPro 4.13.6+R828995c
> >>
> >> 1) Create a new profile
> >> PanelPro Quit and restart
> >> 2) Configure connection
> >> System manufacturer = Roco
> >> System connection = Z21 Simulator
> >> Save and Restart
> >> 3) Tools >> Throttles >> New Throttle >> Enter Address 3 >> Set
> >> After some seconds a window "Failed to create Throttle" shows up,
> saying "Failed to get response from command station"
> >>
> >> All defaults are set to "Z21". I didn't change it.
> >> I'm able to create a JMRI throttle in other simulator modes.
> >
> > Thanks for the additional detail.  I really, really don’t understand the
> Z21 code; it looks to me like it doesn’t create a simulated throttle under
> Z21, but instead in the other two (!) connections that it creates. If I
> change the default throttle to i.e. Z21XpressNet it seems to work:
> >
> >
> >
> > So this is a problem, but it doesn’t seem to be a new problem.
> >
> > Did it used to work for you pre-4.13.6? If so, was that because the
> Internal throttle was being automatically selected as default?
> >
> > it would be a reasonable thing to add a simulated throttle to Z21, like
> many other systems have, but I don’t understand that code well enough to be
> able to do it.
> >
> > Bob
> > --
> > Bob Jacobsen
> > jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
> >
> >
> >
> >
> > _______________________________________________
> > Jmri-developers mailing list
> > Jmr...@li...
> > https://lists.sourceforge.net/lists/listinfo/jmri-developers
> >
> _______________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://lists.sourceforge.net/lists/listinfo/jmri-developers
>

Re: [Jmri-developers] First 4.13.6 files available

[Klaus K. <kla...@t-...>]

Yes, it used to work for me pre-4.13.6. I have a local repository 
4.13.6ish (I think it is from 21 November 2018) where it works.

I have to switch the Preferences >> Defaults from "Z21" to "Internal".

Klaus


Am 06.12.2018 um 11:29 schrieb Bob Jacobsen via Jmri-developers:
> 
> 
>> On Dec 6, 2018, at 12:48 AM, Klaus Killinger <kla...@t-...> wrote:
>>
>> Windows 7, PanelPro 4.13.6+R828995c
>>
>> 1) Create a new profile
>> PanelPro Quit and restart
>> 2) Configure connection
>> System manufacturer = Roco
>> System connection = Z21 Simulator
>> Save and Restart
>> 3) Tools >> Throttles >> New Throttle >> Enter Address 3 >> Set
>> After some seconds a window "Failed to create Throttle" shows up, saying "Failed to get response from command station"
>>
>> All defaults are set to "Z21". I didn't change it.
>> I'm able to create a JMRI throttle in other simulator modes.
> 
> Thanks for the additional detail.  I really, really don’t understand the Z21 code; it looks to me like it doesn’t create a simulated throttle under Z21, but instead in the other two (!) connections that it creates. If I change the default throttle to i.e. Z21XpressNet it seems to work:
> 
> 
> 
> So this is a problem, but it doesn’t seem to be a new problem.
> 
> Did it used to work for you pre-4.13.6? If so, was that because the Internal throttle was being automatically selected as default?
> 
> it would be a reasonable thing to add a simulated throttle to Z21, like many other systems have, but I don’t understand that code well enough to be able to do it.
> 
> Bob
> --
> Bob Jacobsen
> jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
> 
> 
> 
> 
> _______________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://lists.sourceforge.net/lists/listinfo/jmri-developers
> 

Re: [Jmri-developers] Migration of this list to Groups.io - proposal

[Matthew H. <mat...@gm...>]

Dear all,

Given that there has been a flurry of activity on this list, we will wait
for that to calm down before placing this list in read-only mode.

As a reminder, it is necessary for anyone wishing to follow/participate in
JMRI developer discussion to manually subscribe to the new list via web at
https://jmri-developers.groups.io/g/jmri/join or emailing
jmr...@jm...

This is due to SF no longer allowing us to access or export the subscriber
list.

Current plan is to switch THIS list (on SourceForge) to read-only mode some
time around 20h00 UTC today (6th December).

After that time, conversations should take place on the groups.io list.

The list archive will remain here, but we will organise an import of the
archive to groups.io in the meantime.

Best regards,

Matt H


On Fri, 30 Nov 2018 at 23:44, Bob Jacobsen via Jmri-developers <
jmr...@li...> wrote:

> First, I’d like to thank Matt for thinking all this through.
>
> This sounds like a plan that we should implement sooner rather than
> later.
>
> Bob
>
> > On Nov 29, 2018, at 1:32 AM, Matthew Harris <
> mat...@gm...> wrote:
> >
> > Dear all,
> >
> > As some of you may recall, over the last few years, we've been
> experiencing several issues with various aspects of the SourceForge
> infrastructure which has resulted in us migrating the majority of our
> development tool set away to other alternatives.
> >
> > Today, the last parts of the JMRI development tool set that still rely
> on SourceForge are a few of our mailing lists, mainly this one and the
> 'jmri-announce' list.
> >
> > Several months ago, due to reliability issues noticed with the Yahoo!
> platform, we migrated the 'jmriusers' group from Yahoo! Groups to Groups.io.
> >
> > Around that same time, we also created a 'shadow' developers list on
> Groups.io, which was configured to receive copies of all messages posted
> here so as to already start building up an archive of recent activity.
> >
> > Our experience thus far with 'jmriusers' on Groups.io has been positive
> so the time has now come to switch over fully to Groups.io for these last
> remaining lists.
> >
> > Unfortunately, due to restrictions of the SourceForge platform, it's not
> possible for us to retrieve a list of subscribers to the various JMRI
> mailing lists, meaning that it will be necessary to manually subscribe
> yourself to the new list on Groups.io.
> >
> > As a result, there will need to be a cut over period during which
> conversations might end up happening on both lists (this has already
> happened in a few cases) so we need to define a suitable timeline for the
> cut over.
> >
> > My proposal for the cut over is as follows:
> >
> > - Encourage new sign-ups to the new jmri-developers list via web at
> https://jmri-developers.groups.io/g/jmri or by email via
> jmr...@jm...
> > - Place this list into read-only mode after a grace period (say 1 week)
> to minimise risk of conversations in both places
> > - (Optionally) transfer archive of messages from this list
> >
> > Thanks to Bob, we've got a pretty much complete archive of the messages
> from this list in a suitable format so it shouldn't be too much effort to
> get this imported into Groups.io. Given that we've already been building up
> an archive, we might end up with some duplicated messages and some out of
> order, but I'd suggest that's more of an inconvenience than anything else.
> >
> > The new list is configured as a main list (
> jm...@jm...) with sub-groups for specific purposes,
> such as commit messages and infrastructure monitoring, to which you are
> able to optionally subscribe.
> >
> > Please let me know any comments/remarks regarding this proposal so we
> can determine the best route forward.
> >
> > Best regards,
> >
> > Matt H
> > _______________________________________________
> > Jmri-developers mailing list
> > Jmr...@li...
> > https://lists.sourceforge.net/lists/listinfo/jmri-developers
>
> --
> Bob Jacobsen
> jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
>
>
>
> _______________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://lists.sourceforge.net/lists/listinfo/jmri-developers
>

Re: [Jmri-developers] First 4.13.6 files available

[Bob J. <jac...@ma...>]

> On Dec 6, 2018, at 12:48 AM, Klaus Killinger <kla...@t-...> wrote:
> 
> Windows 7, PanelPro 4.13.6+R828995c
> 
> 1) Create a new profile
> PanelPro Quit and restart
> 2) Configure connection
> System manufacturer = Roco
> System connection = Z21 Simulator
> Save and Restart
> 3) Tools >> Throttles >> New Throttle >> Enter Address 3 >> Set
> After some seconds a window "Failed to create Throttle" shows up, saying "Failed to get response from command station"
> 
> All defaults are set to "Z21". I didn't change it.
> I'm able to create a JMRI throttle in other simulator modes.

Thanks for the additional detail.  I really, really don’t understand the Z21 code; it looks to me like it doesn’t create a simulated throttle under Z21, but instead in the other two (!) connections that it creates. If I change the default throttle to i.e. Z21XpressNet it seems to work:



So this is a problem, but it doesn’t seem to be a new problem.

Did it used to work for you pre-4.13.6? If so, was that because the Internal throttle was being automatically selected as default?

it would be a reasonable thing to add a simulated throttle to Z21, like many other systems have, but I don’t understand that code well enough to be able to do it.

Bob
--
Bob Jacobsen
jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG

Re: [Jmri-developers] First 4.13.6 files available

[Klaus K. <kla...@t-...>]

Windows 7, PanelPro 4.13.6+R828995c

1) Create a new profile
  PanelPro Quit and restart
2) Configure connection
  System manufacturer = Roco
  System connection = Z21 Simulator
  Save and Restart
3) Tools >> Throttles >> New Throttle >> Enter Address 3 >> Set
  After some seconds a window "Failed to create Throttle" shows up, 
saying "Failed to get response from command station"

All defaults are set to "Z21". I didn't change it.
I'm able to create a JMRI throttle in other simulator modes.

Klaus


Am 05.12.2018 um 23:54 schrieb Bob Jacobsen via Jmri-developers:
> 
> 
>> On Dec 5, 2018, at 8:59 AM, Klaus Killinger <kla...@t-...> wrote:
>>
>> I'm not able to create a JMRI throttle under Roco Z21 Simulator.
> 
> Could you say a little bit more about this please?  I just tried to do that with a new connection. It worked OK, but perhaps I didn’t configure it the same as you have or something else was different.
> 
> Thanks
> 
> Bob
> --
> Bob Jacobsen
> jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
> 
> 
> 
> _______________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://lists.sourceforge.net/lists/listinfo/jmri-developers
> 

Re: [Jmri-developers] First 4.13.6 files available

[Bob J. <jac...@ma...>]

> On Dec 5, 2018, at 8:59 AM, Klaus Killinger <kla...@t-...> wrote:
> 
> I'm not able to create a JMRI throttle under Roco Z21 Simulator.

Could you say a little bit more about this please?  I just tried to do that with a new connection. It worked OK, but perhaps I didn’t configure it the same as you have or something else was different.

Thanks

Bob
--
Bob Jacobsen
jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG

Re: [Jmri-developers] First 4.13.6 files available

[Dan B. <dab...@ho...>]

More testing, I created a duplicate profile called "Test". It wasn't rejected, and JMRI created a second profile called "Test".  The “2nd Test” has the “same” file pathname  but with the ".jmri" extension.  Not sure if this is an issue?  I can load either one.  Attempted to create a 3rd “Test” profile and that was correctly rejected.



[cid:image001.png@01D48CBC.0D87C950]

Re: [Jmri-developers] First 4.13.6 files available

[Bob J. <jac...@ma...>]

Thank you!  I think I’ve found and fixed that, there will be an update in new files perhaps this evening.

Appreciate you taking the time for the test.

Bob

> On Dec 5, 2018, at 10:01 AM, Bill Chown via Jmri-developers <jmr...@li...> wrote:
> 
> Works fine on Win 10 with an existing profile, but not able to create a new profile for SPROG, as it doesn't offer the Serial Connection field. Seems to work if I pick other systems (Digitrax, Bachrus).

--
Bob Jacobsen
jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG

Re: [Jmri-developers] First 4.13.6 files available

[Dan B. <dab...@ho...>]

Downloaded and installed on Win7.  Loaded panel using NCE simulator, tested turnouts and routes, all good.

Dan

> -----Original Message-----
> From: Bob Jacobsen via Jmri-developers [mailto:jmri-
> dev...@li...]
> Sent: Wednesday, December 05, 2018 10:22 AM
> To: steve young via Jmri-developers <jmr...@li...>
> Cc: Bob Jacobsen <jac...@ma...>
> Subject: [Jmri-developers] First 4.13.6 files available
> 
> First JMRI 4.13.6 files are available in the usual way at:
> 
> https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbuilds.jmri
> .org%2Fjenkins%2Fjob%2FTestReleases%2Fjob%2F4.13.6&amp;data=02%7C01
> %7C%7Cd828e9c6920e453c187108d65ac58f00%7C84df9e7fe9f640afb435aaaa
> aaaaaaaa%7C1%7C0%7C636796201900887290&amp;sdata=ct7mV75EkZkLJdb
> %2FOKKYo3s0qRHv1QYzfhAXYnMM7DM%3D&amp;reserved=0
> 
> Feedback appreciated. Checking that various connections actually work (i.e. that
> internals changes haven’t broken anything) particularly appreciated.
> 
> Bob
> 
> --
> Bob Jacobsen
> jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
> 
> 
> 
> _______________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sour
> ceforge.net%2Flists%2Flistinfo%2Fjmri-
> developers&amp;data=02%7C01%7C%7Cd828e9c6920e453c187108d65ac58f00
> %7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636796201900887290
> &amp;sdata=2y1%2Bulr4rZp7L7ZnF4IslmYn7AlQpJc3ux%2BINlqo9c8%3D&amp;r
> eserved=0

Re: [Jmri-developers] First 4.13.6 files available

[Bob J. <jac...@ma...>]

> On Dec 5, 2018, at 11:36 AM, Andrew Crosland <an...@cr...> wrote:
> 
>   INFO  - DecoderPro version 4.13.5+Rb27c31c starts under Java 1.8.0_151 on Windows 10 amd64 v10.0 at Wed Dec 05 19:21:50 GMT 2018 [main]
> 2018-12-05 19:21:53,580 gui3.Apps3       

This test seems to be running an older version. Was it from one of the new files?

Re: [Jmri-developers] First 4.13.6 files available

[Andrew C. <an...@cr...>]

Forget this, it was a Windows issue. Despite appearing Device Manager, 
COM8 was not functional.

Andrew

------ Original Message ------
From: "Andrew Crosland" <an...@cr...>
To: "Discussions between JMRI developers" 
<jmr...@li...>
Sent: 05/12/2018 19:42:13
Subject: Re[2]: [Jmri-developers] First 4.13.6 files available

>Another test,
>
>With a SPROG on COM8, opened the profile for SPROG on COM6
>
>I was presented with four options selected start with new profile. This 
>time the serial port selector was not populated so I was unable to 
>create a profile. This is similar to the behaviour reported bu Bill.
>
>Andrew
>
>------ Original Message ------
>From: "Bill Chown via Jmri-developers" 
><jmr...@li...>
>To: "Bob Jacobsen via Jmri-developers" 
><jmr...@li...>
>Cc: "Bill Chown" <orr...@ya...>
>Sent: 05/12/2018 18:01:18
>Subject: Re: [Jmri-developers] First 4.13.6 files available
>
>>Works fine on Win 10 with an existing profile, but not able to create 
>>a new profile for SPROG, as it doesn't offer the Serial Connection 
>>field. Seems to work if I pick other systems (Digitrax, Bachrus).
>>Testing some more.
>>
>>Bill
>>
>>Bill Chown
>>orr...@ya...
>>http://bchown.com/ <http://orrrbrit.home.comcast.net>
>>
>>
>>On Wednesday, December 5, 2018, 7:23:11 AM PST, Bob Jacobsen via 
>>Jmri-developers <jmr...@li...> wrote:
>>
>>
>>First JMRI 4.13.6 files are available in the usual way at:
>>
>>http://builds.jmri.org/jenkins/job/TestReleases/job/4.13.6
>>
>>Feedback appreciated. Checking that various connections actually work 
>>(i.e. that internals changes haven’t broken anything) particularly 
>>appreciated.
>>
>>Bob
>>
>>--
>>Bob Jacobsen
>>jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
>>
>>
>>
>>_______________________________________________
>>Jmri-developers mailing list
>>Jmr...@li...
>>https://lists.sourceforge.net/lists/listinfo/jmri-developers

Re: [Jmri-developers] First 4.13.6 files available

[Andrew C. <an...@cr...>]

Another test,

With a SPROG on COM8, opened the profile for SPROG on COM6

I was presented with four options selected start with new profile. This 
time the serial port selector was not populated so I was unable to 
create a profile. This is similar to the behaviour reported bu Bill.

Andrew

------ Original Message ------
From: "Bill Chown via Jmri-developers" 
<jmr...@li...>
To: "Bob Jacobsen via Jmri-developers" 
<jmr...@li...>
Cc: "Bill Chown" <orr...@ya...>
Sent: 05/12/2018 18:01:18
Subject: Re: [Jmri-developers] First 4.13.6 files available

>Works fine on Win 10 with an existing profile, but not able to create a 
>new profile for SPROG, as it doesn't offer the Serial Connection field. 
>Seems to work if I pick other systems (Digitrax, Bachrus).
>Testing some more.
>
>Bill
>
>Bill Chown
>orr...@ya...
>http://bchown.com/ <http://orrrbrit.home.comcast.net>
>
>
>On Wednesday, December 5, 2018, 7:23:11 AM PST, Bob Jacobsen via 
>Jmri-developers <jmr...@li...> wrote:
>
>
>First JMRI 4.13.6 files are available in the usual way at:
>
>http://builds.jmri.org/jenkins/job/TestReleases/job/4.13.6
>
>Feedback appreciated. Checking that various connections actually work 
>(i.e. that internals changes haven’t broken anything) particularly 
>appreciated.
>
>Bob
>
>--
>Bob Jacobsen
>jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
>
>
>
>_______________________________________________
>Jmri-developers mailing list
>Jmr...@li...
>https://lists.sourceforge.net/lists/listinfo/jmri-developers

Re: [Jmri-developers] First 4.13.6 files available

[Andrew C. <an...@cr...>]

I was able to create a new SPROG programmer profile OK on Win 10.

On first startup in programmer (service) mode the status shows "No 
Operations Mode programmer Available" in red, just like it used to do a 
few versions ago.

Shut down and reopen the same profile throws an error:


All of the preferences have been set to internal.

Next I created another new profile and went straight to the defaults. 
They are all set to internal.

Next I set the correct defaults, saved and restarted. It opens OK but 
has now reverted to the confusing Green "Internal" text for the ops 
mpode programmer. So nothing has changed.

Sorry, but this versions is a serious backward step.



Log from the first profile when restarted:

2018-12-05 19:21:50,101 util.Log4JUtil                        INFO  - 
****** JMRI log ******* [main]
2018-12-05 19:21:50,117 util.Log4JUtil                        INFO  - 
This log is appended to file: C:\Users\Daddy\JMRI\log\messages.log 
[main]
2018-12-05 19:21:50,117 util.Log4JUtil                        INFO  - 
This log is stored in file: C:\Users\Daddy\JMRI\log\session.log [main]
2018-12-05 19:21:50,133 apps.AppsBase                         INFO  - 
DecoderPro version 4.13.5+Rb27c31c starts under Java 1.8.0_151 on 
Windows 10 amd64 v10.0 at Wed Dec 05 19:21:50 GMT 2018 [main]
2018-12-05 19:21:53,580 gui3.Apps3                            INFO  - 
Starting with profile SPROG_IIv4_COM6.3ec9cdd4 [main]
2018-12-05 19:21:53,908 node.NodeIdentity                     INFO  - 
Using jmri-gKQIid2VGhNiaacFaMaaaf-3ec9cdd4 as the JMRI Node identity 
[AWT-EventQueue-0]
2018-12-05 19:21:53,986 xml.AbstractSerialConnectionConfigXml INFO  - 
Starting to connect for "SPROG Programmer" [main]
2018-12-05 19:21:54,343 serialdriver.SerialDriverAdapter      INFO  - 
COM6 port opened at 9600 baud, sees  DTR: true RTS: true DSR: false CTS: 
false  CD: false [main]
2018-12-05 19:21:54,733 plementation.JmriConfigurationManager ERROR - 
Exception initializing jmri.managers.ManagerDefaultSelector: JMRI is 
defaulting to internal systems for all purposes. Usually this is 
indicates a misconfiguration. [main]
2018-12-05 19:21:54,749 plementation.JmriConfigurationManager ERROR - 
Exception initializing apps.StartupActionsManager: 
jmri.util.prefs.InitializationException: Unable to run startup actions 
due to earlier failures. [main]
2018-12-05 19:23:51,952 util.FileUtilSupport                  INFO  - 
File path program: is C:\Program Files (x86)\JMRI\ [main]
2018-12-05 19:23:51,954 util.FileUtilSupport                  INFO  - 
File path preference: is C:\Users\Daddy\JMRI\SPROG_IIv4_COM6.jmri\ 
[main]
2018-12-05 19:23:51,954 util.FileUtilSupport                  INFO  - 
File path profile: is C:\Users\Daddy\JMRI\SPROG_IIv4_COM6.jmri\ [main]
2018-12-05 19:23:51,955 util.FileUtilSupport                  INFO  - 
File path settings: is C:\Users\Daddy\JMRI\ [main]
2018-12-05 19:23:51,956 util.FileUtilSupport                  INFO  - 
File path home: is C:\Users\Daddy\ [main]
2018-12-05 19:23:51,957 util.FileUtilSupport                  INFO  - 
File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main]
2018-12-05 19:23:52,779 gui3.TabbedPreferencesAction          INFO  - We 
are already waiting for the preferences to be displayed [main]
2018-12-05 19:23:54,674 throttle.ThrottlesPreferences         INFO  - 
Did not find throttle preferences file.  This is normal if you haven't 
save the preferences before [TabbedPreferencesAction actionPerformed]
2018-12-05 19:23:54,674 hrottle.AbstractWiThrottlePreferences INFO  - 
Could not find WiThrottle preferences file 
(C:\Users\Daddy\JMRI\SPROG_IIv4_COM6.jmri\throttle\WiThrottlePreferences.xml). 
  Normal if preferences have not been saved before. 
[TabbedPreferencesAction actionPerformed]
2018-12-05 19:24:05,108 throttle.ThrottlesPreferences         INFO  - 
Did not find throttle preferences file.  This is normal if you haven't 
save the preferences before [AWT-EventQueue-0]
2018-12-05 19:24:05,108 jmrit.XmlFile                         INFO  - No 
C:\Users\Daddy\JMRI\SPROG_IIv4_COM6.jmri\throttle\ThrottlesPreferences.xml 
file to backup [AWT-EventQueue-0]
2018-12-05 19:24:05,531 jmrit.XmlFile                         INFO  - No 
C:\Users\Daddy\JMRI\SPROG_IIv4_COM6.jmri\throttle\WiThrottlePreferences.xml 
file to backup [AWT-EventQueue-0]



------ Original Message ------
From: "Bill Chown via Jmri-developers" 
<jmr...@li...>
To: "Bob Jacobsen via Jmri-developers" 
<jmr...@li...>
Cc: "Bill Chown" <orr...@ya...>
Sent: 05/12/2018 18:01:18
Subject: Re: [Jmri-developers] First 4.13.6 files available

>Works fine on Win 10 with an existing profile, but not able to create a 
>new profile for SPROG, as it doesn't offer the Serial Connection field. 
>Seems to work if I pick other systems (Digitrax, Bachrus).
>Testing some more.
>
>Bill
>
>Bill Chown
>orr...@ya...
>http://bchown.com/ <http://orrrbrit.home.comcast.net>
>
>
>On Wednesday, December 5, 2018, 7:23:11 AM PST, Bob Jacobsen via 
>Jmri-developers <jmr...@li...> wrote:
>
>
>First JMRI 4.13.6 files are available in the usual way at:
>
>http://builds.jmri.org/jenkins/job/TestReleases/job/4.13.6
>
>Feedback appreciated. Checking that various connections actually work 
>(i.e. that internals changes haven’t broken anything) particularly 
>appreciated.
>
>Bob
>
>--
>Bob Jacobsen
>jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
>
>
>
>_______________________________________________
>Jmri-developers mailing list
>Jmr...@li...
>https://lists.sourceforge.net/lists/listinfo/jmri-developers

Re: [Jmri-developers] First 4.13.6 files available

[Bill C. <orr...@ya...>]

Works fine on Win 10 with an existing profile, but not able to create a new profile for SPROG, as it doesn't offer the Serial Connection field. Seems to work if I pick other systems (Digitrax, Bachrus).Testing some more.
Bill
Bill Cho...@ya...://bchown.com/ 

    On Wednesday, December 5, 2018, 7:23:11 AM PST, Bob Jacobsen via Jmri-developers <jmr...@li...> wrote:  
 
 First JMRI 4.13.6 files are available in the usual way at:

http://builds.jmri.org/jenkins/job/TestReleases/job/4.13.6

Feedback appreciated. Checking that various connections actually work (i.e. that internals changes haven’t broken anything) particularly appreciated.

Bob

--
Bob Jacobsen
jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG



_______________________________________________
Jmri-developers mailing list
Jmr...@li...
https://lists.sourceforge.net/lists/listinfo/jmri-developers
  

Re: [Jmri-developers] First 4.13.6 files available

[Dave S. <da...@sa...>]

Works fine on macOS 10.14.1 using simulation modes.

Dave Sand



> On Dec 5, 2018, at 9:22 AM, Bob Jacobsen via Jmri-developers <jmr...@li...> wrote:
> 
> First JMRI 4.13.6 files are available in the usual way at:
> 
> http://builds.jmri.org/jenkins/job/TestReleases/job/4.13.6
> 
> Feedback appreciated. Checking that various connections actually work (i.e. that internals changes haven’t broken anything) particularly appreciated.
> 
> Bob
> 
> --
> Bob Jacobsen
> jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
> 
> 
> 
> _______________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://lists.sourceforge.net/lists/listinfo/jmri-developers

Re: [Jmri-developers] First 4.13.6 files available

[Klaus K. <kla...@t-...>]

Installed on Windows 7 (Digitrax LocoNet Simulator and LocoBuffer-USB), 
looks good.

I'm not able to create a JMRI throttle under Roco Z21 Simulator.

Klaus


Am 05.12.2018 um 16:22 schrieb Bob Jacobsen via Jmri-developers:
> First JMRI 4.13.6 files are available in the usual way at:
> 
> http://builds.jmri.org/jenkins/job/TestReleases/job/4.13.6
> 
> Feedback appreciated. Checking that various connections actually work (i.e. that internals changes haven’t broken anything) particularly appreciated.
> 
> Bob
> 
> --
> Bob Jacobsen
> jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
> 
> 
> 
> _______________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://lists.sourceforge.net/lists/listinfo/jmri-developers
> 

[Jmri-developers] First 4.13.6 files available

[Bob J. <jac...@ma...>]

First JMRI 4.13.6 files are available in the usual way at:

http://builds.jmri.org/jenkins/job/TestReleases/job/4.13.6

Feedback appreciated. Checking that various connections actually work (i.e. that internals changes haven’t broken anything) particularly appreciated.

Bob

--
Bob Jacobsen
jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG

Re: [Jmri-developers] System Connection Memo question

[steve y. <ick...@ya...>]

Hi Balazs,
The only issue I have with the Can System connection is the behaviour shown in https://github.com/JMRI/JMRI/issues/6124
On an OpenLCB Network connection is the text remaining black when the connection is down?

 Ta,
Steve.

Re: [Jmri-developers] Migration of this list to Groups.io - proposal

[Bob J. <jac...@ma...>]

First, I’d like to thank Matt for thinking all this through.

This sounds like a plan that we should implement sooner rather than later.  

Bob

> On Nov 29, 2018, at 1:32 AM, Matthew Harris <mat...@gm...> wrote:
> 
> Dear all,
> 
> As some of you may recall, over the last few years, we've been experiencing several issues with various aspects of the SourceForge infrastructure which has resulted in us migrating the majority of our development tool set away to other alternatives.
> 
> Today, the last parts of the JMRI development tool set that still rely on SourceForge are a few of our mailing lists, mainly this one and the 'jmri-announce' list. 
> 
> Several months ago, due to reliability issues noticed with the Yahoo! platform, we migrated the 'jmriusers' group from Yahoo! Groups to Groups.io.
> 
> Around that same time, we also created a 'shadow' developers list on Groups.io, which was configured to receive copies of all messages posted here so as to already start building up an archive of recent activity.
> 
> Our experience thus far with 'jmriusers' on Groups.io has been positive so the time has now come to switch over fully to Groups.io for these last remaining lists.
> 
> Unfortunately, due to restrictions of the SourceForge platform, it's not possible for us to retrieve a list of subscribers to the various JMRI mailing lists, meaning that it will be necessary to manually subscribe yourself to the new list on Groups.io.
> 
> As a result, there will need to be a cut over period during which conversations might end up happening on both lists (this has already happened in a few cases) so we need to define a suitable timeline for the cut over.
> 
> My proposal for the cut over is as follows:
> 
> - Encourage new sign-ups to the new jmri-developers list via web at https://jmri-developers.groups.io/g/jmri or by email via jmr...@jm...
> - Place this list into read-only mode after a grace period (say 1 week) to minimise risk of conversations in both places
> - (Optionally) transfer archive of messages from this list
> 
> Thanks to Bob, we've got a pretty much complete archive of the messages from this list in a suitable format so it shouldn't be too much effort to get this imported into Groups.io. Given that we've already been building up an archive, we might end up with some duplicated messages and some out of order, but I'd suggest that's more of an inconvenience than anything else.
> 
> The new list is configured as a main list (jm...@jm...) with sub-groups for specific purposes, such as commit messages and infrastructure monitoring, to which you are able to optionally subscribe.
> 
> Please let me know any comments/remarks regarding this proposal so we can determine the best route forward.
> 
> Best regards,
> 
> Matt H
> _______________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://lists.sourceforge.net/lists/listinfo/jmri-developers

--
Bob Jacobsen
jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG

Re: [Jmri-developers] Layout Scales

[Donald K. <ki...@sr...>]

From: Dave Sand 
The new plan is to move the scale data to an XML file stored at program:resources/scales/ScaleData.xml.  The ScaleManager would load the XML file instead of having a hard coded list.

When a custom user name and/or ratio is supplied, the xml file is copied to preference:resources/scales and modified.  The user version takes precedence.  This approach also makes it possible for a user to create their own scale list by adding, changing or deleting entries.


Dave Sand




Will there be something to change from an older version to read the values now used if the ScaleData.xml is not found when the program is run?
Thinking of headaches when someone upgrades from an older version.

Donald

Re: [Jmri-developers] Layout Scales

[Dave S. <da...@sa...>]

I am now working on version 2 of the Scale project.

A requirement of the TimeTable project is the ability to veto scale ratio changes that would result in TimeTable errors.  To accomplish this, the scale data is being changed from an Enum to a class based on jmri.beans.ConstrainedBean.  The services supplied by the Enum are handled by ScaleManager and Scale becomes an instance of one scale.

The other change deals with custom data persistence.  The current concept uses the profile user-interface.xml file.  This introduces issues since it is tied to a specific profile and node-id.

The new plan is to move the scale data to an XML file stored at program:resources/scales/ScaleData.xml.  The ScaleManager would load the XML file instead of having a hard coded list.

When a custom user name and/or ratio is supplied, the xml file is copied to preference:resources/scales and modified.  The user version takes precedence.  This approach also makes it possible for a user to create their own scale list by adding, changing or deleting entries.


Dave Sand

[Jmri-developers] Migration of this list to Groups.io - proposal

[Matthew H. <mat...@gm...>]

Dear all,

As some of you may recall, over the last few years, we've been experiencing
several issues with various aspects of the SourceForge infrastructure which
has resulted in us migrating the majority of our development tool set away
to other alternatives.

Today, the last parts of the JMRI development tool set that still rely on
SourceForge are a few of our mailing lists, mainly this one and the
'jmri-announce' list.

Several months ago, due to reliability issues noticed with the Yahoo!
platform, we migrated the 'jmriusers' group from Yahoo! Groups to Groups.io.

Around that same time, we also created a 'shadow' developers list on
Groups.io, which was configured to receive copies of all messages posted
here so as to already start building up an archive of recent activity.

Our experience thus far with 'jmriusers' on Groups.io has been positive so
the time has now come to switch over fully to Groups.io for these last
remaining lists.

Unfortunately, due to restrictions of the SourceForge platform, it's not
possible for us to retrieve a list of subscribers to the various JMRI
mailing lists, meaning that it will be necessary to manually subscribe
yourself to the new list on Groups.io.

As a result, there will need to be a cut over period during which
conversations might end up happening on both lists (this has already
happened in a few cases) so we need to define a suitable timeline for the
cut over.

My proposal for the cut over is as follows:

- Encourage new sign-ups to the new jmri-developers list via web at
https://jmri-developers.groups.io/g/jmri or by email via
jmr...@jm...
- Place this list into read-only mode after a grace period (say 1 week) to
minimise risk of conversations in both places
- (Optionally) transfer archive of messages from this list

Thanks to Bob, we've got a pretty much complete archive of the messages
from this list in a suitable format so it shouldn't be too much effort to
get this imported into Groups.io. Given that we've already been building up
an archive, we might end up with some duplicated messages and some out of
order, but I'd suggest that's more of an inconvenience than anything else.

The new list is configured as a main list (jm...@jm...)
with sub-groups for specific purposes, such as commit messages and
infrastructure monitoring, to which you are able to optionally subscribe.

Please let me know any comments/remarks regarding this proposal so we can
determine the best route forward.

Best regards,

Matt H

Re: [Jmri-developers] 4.13.5 tested

[Bill C. <orr...@ya...>]

Dave,thank you for the offer of builds to test. Due to hardware changes, I do not have a current build environment set up, and so will definitely use any build - for all platforms - that I can test with all the SPROG family.Thank you
Bill


Bill Cho...@ya...://bchown.com/ 

    On Monday, November 26, 2018, 8:29:33 PM PST, Dave Heap <dg...@gm...> wrote:  
 
 Bill,

Bob Jacobsen has been putting a huge amount of work into this Internal issue and I have been testing the results in a branch he is working on. In fact, I'm doing tests right now. See the following:https://github.com/JMRI/JMRI/pull/6161
If you'd like to do some testing of your own, I can easily create private builds of the Mac/Windows/Linux installer packages from the latest state of this branch for you to install and do some of your own testing. The more testing it gets, the more likely we are to arrive at a the correct solution for all possibilities. Just let me know...

Sent from my iPad
-- 
Dave Heap



On 27 Nov 2018, at 2:36 PM, Bill Chown via Jmri-developers <jmr...@li...> wrote:





I ran a few SPROG tests and this works fine. However I am disappointed to still see the bogus Green message suggesting the Internal Programmer is online. Back to the old RED message, PLEASE!