[Xastir] A few changes

[David Ranch]

I've build and installed the Git master branch (5/1/19) here on Centos 
6.10 and it seems to be running ok but a few things:

    1. In the Help --> About window,

       1.a  it's NOT showing the Git version as this thread talks about 
(attaching a screen capture to this email - let's see if it makes it)

       1.b  Shows they year 2018

    2. No errors are showing from STDOUT upon start or graceful exit

    3. No stray Xastir processes found upon graceful exit

So far, the zoom in/out and panning is working fine.

--David
KI6ZHD




On 04/30/2019 08:23 AM, km5vy Tom Russo wrote:
> On Tue, Apr 30, 2019 at 08:09:21AM -0700, we recorded a bogon-computron collision of the <curt.we7u at gmail.com> flavor, containing:
>> Yes on the NWS script being up-to-date. With all the places the code has
>> been tweaked recently I'd like to see the dust settle for a few weeks. Give
>> us time to test out all the different types of maps. I'd like to see
>> messaging tested as well. Having a bunch of users pound on it is probably
>> the best method because everybody uses Xastir in different ways.
>
> Yeah, we should probably be considering the current state of master as a
> release candidate, and anyone who can possibly pull it down, build it, and
> feed back any new bugs should do so.
>
> My point, though, is that we should probably be slowing down on these tweaks
> (we've really done a ton of work in the last couple of weeks), and when the
> dust settles and we get some confirmation that there's no new breakagee,
> we should call it 2.1.2 without further ado.
>
>> On Tue, Apr 30, 2019 at 8:04 AM Tom Russo <russo at bogodyn.org> wrote:
>>
>>> On Tue, Apr 30, 2019 at 07:58:26AM -0700, we recorded a bogon-computron
>>> collision of the <curt.we7u at gmail.com> flavor, containing:
>>>> 2) In the Help->About dialog you'll see at the very top something like:
>>>>
>>>>      Xastir V2.1.1 (cf75dd5a)
>>>>
>>>> That last number is the 8-digit short-form version of the most recent Git
>>>> commit. That tells you _exactly_ which code is in your compile.
>>> This is not a recent change.  It's been happening since August 2017.  It is
>>> automatically enabled if you're building the code from a git clone instead
>>> of a tarball.
>>>
>>>> 6) The project is currently at zero pull requests and only a few
>>>> outstanding bugs.
>>>> https://github.com/Xastir/Xastir
>>> I'd say that once we get some feedback about whether bug #66 is still a
>>> problem (Xastir crashing when zooming in and out with OSM maps enabled),
>>> we're probably ready to start kicking release 2.1.2 out of the nest.  Are
>>> the
>>> NWS and other download scripts up to date?  For 2.1.0, NWS changed the
>>> download
>>> site really soon after the release, so perhaps this is always going to be
>>> a moving target.
>>>
>>> --
>>> Tom Russo    KM5VY
>>> Tijeras, NM
>>>
>>>   echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
>>> [n-z][a-m]