Custom XCI file - Bug

[kabmorgan]

Dear All

I'll put this on the bug list as well.

This is a bit deep for most users but it has been driving me bonkers.  I like using my own XCI file and am continually updating it.  I ran into this problem which I have now managed to narrow down to the root cause.

The problem concerns putting custom instructions in screen positions 1,2,3,4, along the bottom of the screen, and the effect they have on what is displayed in postions 8,9, on the RHS of the screen.

If one or two custom instructions are put in positions 1,2,3 or 4 then all is well and positions 8,9 behave themselves.

If three custom instructions are put in positions 1,2,3 or 4 then position 9 will display whatever is in the default file, NOT what is defined in the custom file.

If four custom instructions are put in positions 1,2,3 and 4 then positions 8 and 9 will display whatever is in the default file, NOT what is defined in the custom file.

Took a while to figure this out.  Not happy that I can't use the latest version of my XCI file, but at least I now know what is going on.

Keith

[kabmorgan]

Having spent a lot of time isolating this bug, I now find there is a simple workaround.

The problem only appears when the custom xci mode has the same name as the default mode e.g. Nav1, Display2 etc. Make the name of the customised mode unique and it will bypass the problem e.g. Nav3, Landout, or whatever.

I'll put this on the wiki

Keith

Retrieved from "http://www.xcsoar.org/mediawiki/index.php/Advanced:Input"

kabmorgan wrote:

Dear All

I'll put this on the bug list as well.

This is a bit deep for most users but it has been driving me bonkers.  I like using my own XCI file and am continually updating it.  I ran into this problem which I have now managed to narrow down to the root cause.

The problem concerns putting custom instructions in screen positions 1,2,3,4, along the bottom of the screen, and the effect they have on what is displayed in postions 8,9, on the RHS of the screen.

If one or two custom instructions are put in positions 1,2,3 or 4 then all is well and positions 8,9 behave themselves.

If three custom instructions are put in positions 1,2,3 or 4 then position 9 will display whatever is in the default file, NOT what is defined in the custom file.

If four custom instructions are put in positions 1,2,3 and 4 then positions 8 and 9 will display whatever is in the default file, NOT what is defined in the custom file.

Took a while to figure this out.  Not happy that I can't use the latest version of my XCI file, but at least I now know what is going on.

Keith

[John Wharington-3]

It's not a bug as such, if you re-use existing labels then of course you
are going to have some mix or existing and new functions.

If you want to start from scratch, start your xci file with:
#CLEAR

But make sure you have appropriate menu items for such things as
accessing the configuration menu and exit!

The working xci file that is compiled into XCSoar is always available on
CVS at source/Common/Data/Input/default.xci so this should always be
used as a reference when creating new xci files.

Keith, if you're happy enough with this text could you add it also to
the wiki?

Cheers


johnny

On Wed, 2008-06-25 at 01:07 -0700, kabmorgan wrote:

> Having spent a lot of time isolating this bug, I now find there is a simple
> workaround.
>
> The problem only appears when the custom xci mode has the same name as the
> default mode e.g. Nav1, Display2 etc. Make the name of the customised mode
> unique and it will bypass the problem e.g. Nav3, Landout, or whatever.
>
> I'll put this on the wiki
>
> Keith
>
> Retrieved from "http://www.xcsoar.org/mediawiki/index.php/Advanced:Input"
>
> kabmorgan wrote:
> >
> > Dear All
> >
> > I'll put this on the bug list as well.
> >
> > This is a bit deep for most users but it has been driving me bonkers.  I
> > like using my own XCI file and am continually updating it.  I ran into
> > this problem which I have now managed to narrow down to the root cause.
> >
> > The problem concerns putting custom instructions in screen positions
> > 1,2,3,4, along the bottom of the screen, and the effect they have on what
> > is displayed in postions 8,9, on the RHS of the screen.
> >
> > If one or two custom instructions are put in positions 1,2,3 or 4 then all
> > is well and positions 8,9 behave themselves.
> >
> > If three custom instructions are put in positions 1,2,3 or 4 then position
> > 9 will display whatever is in the default file, NOT what is defined in the
> > custom file.
> >
> > If four custom instructions are put in positions 1,2,3 and 4 then
> > positions 8 and 9 will display whatever is in the default file, NOT what
> > is defined in the custom file.
> >
> > Took a while to figure this out.  Not happy that I can't use the latest
> > version of my XCI file, but at least I now know what is going on.
> >
> > Keith
> >
>

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Xcsoar-devel mailing list
Xcsoar-devel@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-devel