On Sun, Oct 12, 2014 at 2:21 PM, Anton Lundin <[email protected]> wrote:
> On 12 October, 2014 - Dirk Hohndel wrote: > > > On Sun, Oct 12, 2014 at 04:55:00PM +0200, Anton Lundin wrote: > > > On 12 October, 2014 - Anton Lundin wrote: > > > > > > > This builds up a ui to use for all the settings for the Suunto Vyper > > > > family devices. Some of the fields are pure information, eg, max > depth > > > > and number of dives, so they are marked read-only. > > > > > > > > > > I would love if someone with a better knowledge about qt could answer > > > this: > > > > > > Can you re-use common fields between the two different tab widgets, eg > > > Serial number, Custom Text and so on between the OSTC3 and the Suunto > > > Vyper configuration panels? > > not in a easy way, unless it's the same dialog ( then we can just create a class with it and reuse ) normally it's just more trouble than it's worth it. > > Tomaz? Thiago? > > > > > In this patch i just add another set of the same ones. Is that the > right > > > way to do it? > > > > I don't know a different way. This is a cool patch series. Thanks. > > I'm doing test builds right now and expect to push it in a minute. > > Sadly I don't have access to one of those older devices (Tomaz has my > > Mosquito, Linus' Gekko got lost... the other Suuntos I have access to are > > the newer ones like Linus' Vyper Air and HelO₂), so I can't test it. > > > > I've poked Robert and Miika and from what i could read between the lines > they both had something compatible. > > I've have gotten the question about how "safe" the code is to run > against a device, and I've ran the code against my Suunto Vyper without > bricking it, and i wrote some strange things to it while developing the > code so it should be considered as pretty safe. > > > //Anton > > > -- > Anton Lundin +46702-161604 > _______________________________________________ > subsurface mailing list > [email protected] > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface >
_______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
