Re: Mouse event problems

[Tyson Sawyer]

On Fri, Mar 25, 2016 at 1:44 PM, Ken D'Ambrosio  wrote:
> That *VERY* much sounds like hardware.  Like, a lot.
>
> 1) If it's a wireless mouse, change the batteries.
>
> If it's *not* wireless, disable the trackpad and switch to a different
> external mouse.  Assuming the issue goes away (which I bet it will),
> re-enable one, then the other, and see who's at fault.

This is looking like the cause.  I haven't had a chance to use a
different mouse (track ball), but:

- Changed the batteries: no improvement.
- Unplug it or turn it off when problems arise and use the track pad:
much improvement.

It appears to be a problem with the buttons.  I'm not sure exactly
what is going on, but the ability to "clear" the problem by switching
to a VC and back (and other behavior apparently more complex than a
pointer device can "know about") may be something along the lines of
causing the UI to "forget" that a button down event had been inflicted
on some widget on the screen.

Thanks!

-- 
Tyson D Sawyer

A strong conviction that something must be done is the parent
of many bad measures.   - Daniel Webster
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Re: Govt Source Code Policy

[Richard Kolb II]

The years I spent writing software for defense contractors tells me that
the SW is marked 'copyright ' all over it. Paid for with
tax dollars or not, the company that wrote it does it's best to keep the
copyright for it.

IMO this is going to run into the same issue that GPL has, someone is going
to take this and make money off of it and the people giving it out are
going to get angry and change their mind. I believe that is why GPL is
being replaced by non-free licenses. The developers are seeing the work
they did for free make money for someone else, once the government sees
that they'll go the same route.

Rich


Richard Kolb II

On Sun, Mar 27, 2016 at 12:54 PM, Matt Minuti  wrote:

> On Fri, Mar 25, 2016 at 4:59 PM, Greg Rundlett (freephile) <
> g...@freephile.com> wrote:
>
>> Code written by Govt. employees is 'Public Domain', meaning specifically
>> exempted from copyright.
>>
>> However, most? government software is written by contractors, and not
>> published or shared.  I don't know for sure, but I imagine that a large
>> amount of that work is under a proprietary license.  I think it's a giant
>> step in the right direction to get the Govt. to publish, and reuse (our)
>> software because we are paying for it once already.  However, I think that
>> the primary beneficiaries will be the software ISVs and VARs that will
>> essentially have another 'github' of govt. software to grab and bring
>> in-house.  The same problem is reflected at GitHub where the majority of
>> new projects are selecting non-free licenses now whereas a few years ago
>> GPL was the most popular license in the world.
>>
>
> It's overwhelmingly proprietary. In fact, when responding to RFQs/RFPs,
> the contracting agency asks for a clear description of what the IP rights
> are, who gets what kind of ownership and transferability, and so forth. Not
> just software, but the products of research, inventions as a result of the
> work, methods, applications, you name it.
>
> When I wrote the proposal for BlocksCAD, I made certain that all the work
> would be contractually obligated to be open source. Thankfully I was able
> to get it released GPL before I left the company. I was going to release
> the server side AGPL, but I got some serious pushback on that one, and it
> seems like it's still not open at all. Last I was involved, the software
> and training materials were going to be added to the DARPA Open Catalog (
> http://opencatalog.darpa.mil/) but it looks like that might have fallen
> by the wayside, unfortunately.
>
> An interesting thing I learned in the process: at the very least, DARPA
> loves open source. They can feel safer using it on secure systems because
> it can be verified, and it has a low "sustainment risk," that is, the
> company can't suddenly decide to raise the price now that they have a
> captive audience, and if the company goes under, the government can keep
> using it without worrying about acquiring more licenses or anything.
>
> ___
> gnhlug-discuss mailing list
> gnhlug-discuss@mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
>
>
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/