[Xastir] WMSradar Transparency

[Tom Russo]

On Fri, Sep 15, 2006 at 02:30:35PM -0400, we recorded a bogon-computron collision of the <n1mie at myeastern.com> flavor, containing:
> On Sep 15, 2006, at 14:16, Tom Russo wrote:
> 
> >Are you running CVS xastir or one of the releases?
> 
> CVS on the latest update as of sometime this morning.

[...]

> >On unpredictable occasions, the pixel value comes back 0x000000  
> >instead.  But these cases have been rare over the last few months.
> >
> >Setting TRANSPARENT 0x010101 in WMSRadar.geo (as it currently is in  
> >CVS) has been working on 16 and 24 bit displays for several months  
> >(I test it on both). If you're running one of those color depths  
> >and are seeing opaque backgrounds, then either:
> >  - There is some difference between your 16 or 24 bit display and  
> >the two I test on.
> >  - The WMS server is returning 0x000000 background pixels again  
> >--- it probably won't do so for very long.
> 
> Or possibly the CVS update slipped in a 0x000000 as that is what this  
> was compiled against this morning (-r RELEASE).
                                     ^^^^^^^^^^

[affecting best mechanic's demeanor] Welllllllll, *therrrrre's* yer problem.

Adding "-r RELEASE" to a cvs checkout or update is NOT the same as getting the
latest CVS code, no matter how often you do a cvs update.  It selects the 
version that was last tagged for release, or in other words, the last official 
release version.  Any subsequent update done to that directory will ONLY get 
you changes that are also tagged with RELEASE (e.g. next time we do an official 
release a cvs update in that directory will get you the new release) but until 
then it won't update anything at all, because once you specify an "-r" tag that 
tag is "sticky" and applies to all future updates.

The last version of WMSRadar.geo tagged with RELEASE was revision 1.7, and 
was created on June 17, 200*5*.  The revision in which the transparency value 
was changed to 0x010101 was revision 1.8, committed on June 11th, 2006.

To get the honest-to-God latest version of the CVS tree, you need to do:
  cvs update -A
which will unset the sticky tag and update to the latest revision of everything.

If you want new features that are not in the official release, there are two
options: use the "STABLE" tag instead, or use no tag at all:
  cvs update -r STABLE
or 
  cvs update -A   (the first time only, to clear the sticky tag)

The correct version of WMSRadar.geo is present in both the STABLE and 
development versions.

> Yes, it's definitely 0x010101 right now, but that isn't what was in  
> my geo file for some reason.

Because in effect you're really running Xastir version 1.8.0, the last 
official release.  With "-r STABLE" you'd get to 1.8.2.  With "-A" (or a 
fresh checkout with no -r) you'll get the true unstable development version
(which will claim to be "1.8.3" but changes from day to day so the actual
version number is sorta meaningless).

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick