Re: [Jmri-developers] JMRI 4.7.0 and 4.7.1

[Walter T. <wal...@gm...>]

Randall:
I went back to 4.6 to change the Preferences. 4.7.0 would not let me into
them.
I first deleted the connection to Digitrax in 4.6 then tried 4.7.0, Got
looked like the same errors.
Went back to 4.6 and removed my start up actions in the Prefences. Then
4.7.0 starts with out the errors.
Hope that helps!
I had a number of actions on start up., Open Panel file, JMRI restart, Open
programmers (On Main & Programing track, Check version. I think that it.

Walt

On Sun, Feb 26, 2017 at 9:09 AM, Randall Wood <
ran...@al...> wrote:

> Please try using a new profile with 4.7.0.
>
> These failures are *not* from within a panel file, but are from the
> profile startup settings. To be completely honest, problems with the
> profile *are expected* in 4.7.0 (how it refers to serial ports has changed)
> although this particular problem was not anticipated.
>
> Randall Wood
> JMRI Developer - http://jmri.org
> Alexandria Software - http://alexandriasoftware.com
> Northern Virginia NTRAK - http://nvntrak.org
>
>
>
>
> On Feb 26, 2017, at 09:35, Walter Thompson <walter.stanley.thompson.3@
> gmail.com> wrote:
>
> Users can still go back, JMRI saves the Panel files as they are updated in
> the Backup folder, It is a little more work to get back, but the old pane
> files are there. Maybe the reason it fails for me is that I had saved the
> panel file when running 4.7.2
> Walt
>
> On Sun, Feb 26, 2017 at 7:51 AM, Balazs Racz <bal...@gm...>
> wrote:
>
>>
>>
>> On Sun, Feb 26, 2017 at 2:41 PM, Paul Bender <pau...@ac...> wrote:
>>
>>> On 02/25/2017 11:05 PM, Walter Thompson wrote:
>>> > Bob:
>>> > Could the problem I had with 4.7.0 been because I was running bleeding
>>> > edge 4.7.2?
>>> > Walt
>>>
>>> That's possible.  Rememeber that 4.7.0 is 4.6.0 plus the PJC library
>>> changes, no differences otherwise.
>>>
>>> The 4.7.1 build (and the head of master) includes other changes that may
>>> have made changes to the way that the xml files were stored. Storing
>>> files with that version and then going backwards in version could have
>>> caused
>>
>>
>> This will turn into a problem though in the field as well, right?
>> Our users expect to have the ability to switch between versions back and
>> forth (within some reasonable limits), so if 4.7.1 breaks compatibility to
>> 4.6.0 that's not great.
>> I guess it would be important to know whether the XML changes were caused
>> by unsubmitted code in development, or is there a change in the release
>> that edits XML files in a non-backwards-compatible way?
>>
>> Balazs
>>
>>
>>> the errors, most of which are xml related.
>>>
>>> Paul
>>>
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Jmri-developers mailing list
>>> Jmr...@li...
>>> https://lists.sourceforge.net/lists/listinfo/jmri-developers
>>>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Jmri-developers mailing list
>> Jmr...@li...
>> https://lists.sourceforge.net/lists/listinfo/jmri-developers
>>
>>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot______
> _________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://lists.sourceforge.net/lists/listinfo/jmri-developers
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://lists.sourceforge.net/lists/listinfo/jmri-developers
>
>