deco switch issue [was Re: we'll need to release a 5.0.7 pretty soon]

There were a couple of small changes to the deco code since 5.0.7 - it's possible that this was fixed as a part of that. Again, thanks for reporting back. I'll add this to the "problem solved" pile :) /D > On Jun 14, 2022, at 5:58 AM, Steve wrote: > > The "Deco switch at" column is now showin

Re: we'll need to release a 5.0.7 pretty soon

On Sun, 2022-06-12 at 20:01 -0700, Dirk Hohndel wrote: > And... my guess was right... > > Whenever I see bugs for the deco code, I assume that Robert will look > into them (as he's our resident physics professor maintaining this > code)... > > Not a good excuse, but it's the one that I have :)

Re: we'll need to release a 5.0.7 pretty soon

And... my guess was right... Whenever I see bugs for the deco code, I assume that Robert will look into them (as he's our resident physics professor maintaining this code)... Not a good excuse, but it's the one that I have :) /D > On Jun 12, 2022, at 6:31 PM, Steve wrote: > > > Just bringin

Re: we'll need to release a 5.0.7 pretty soon

Just bringing this back up again see attached screenshot for visual for the deco switch at being different for the 2 100% o2 tanks (which should show 6m) and the same deco switch at for the 24% EAN the 21% Air tanks. My guess is not all of those fields are not getting updated &/or calculated corr

Re: we'll need to release a 5.0.7 pretty soon

I played around a bit and noticed these things. The deco switch column doesn't really work at all outside the planner. It'll display the stored depth attribute, which might be wrong, and won't recalculate it. On most of my dives the value seems to have been calculated and saved properly, but I

Re: we'll need to release a 5.0.7 pretty soon

On Samstag, 19. März 2022 06:00:55 CET you wrote: > What does the "Bin" mean in the strings? stats/statsstate.cpp:21 > Looking at the source file does not really help me to understand... As Dirk notes, these are the classes of histograms: https://en.wikipedia.org/wiki/Data_binning https://en.wiki

Re: we'll need to release a 5.0.7 pretty soon

Ugh. This sounds problematic - but I can’t quite figure out WHAT it’s telling me… Anyone else who can help me parse this? /D > On Mar 18, 2022, at 2:34 PM, Steve Williams wrote: > > Something I noticed while looking at the new sensor code was the Deco switch > depth in equipment tab is randoml

Re: we'll need to release a 5.0.7 pretty soon

When you are creating statistics, bins allow you to group things. For example when one of your variables is mean depth, you can bin this in 5m increments. Does that make more sense? Play with the statistics function and it should immediately make sense /D > On Mar 18, 2022, at 10:00 PM, Miika

Re: we'll need to release a 5.0.7 pretty soon

What does the "Bin" mean in the strings? stats/statsstate.cpp:21 Looking at the source file does not really help me to understand... On Fri, Mar 18, 2022 at 6:22 PM Dirk Hohndel via subsurface < subsurface@subsurface-divelog.org> wrote: > I pushed a draft for the announcement (yay, this time I re

Re: we'll need to release a 5.0.7 pretty soon

Something I noticed while looking at the new sensor code was the Deco switch depth in equipment tab is randomly wrong for some tanks. I might not have internet for 4-5 daysSent from mobile ___ subsurface mailing list subsurface@subsurface-divelog.org http

Re: we'll need to release a 5.0.7 pretty soon

Salva, As always. THANK YOU. I so appreciate your support. /D > On Mar 18, 2022, at 12:52 PM, Salvador Cuñat wrote: > > Hi Dirk. > > Spanish strings are up to date right now. > PR sent for the draft announcement. ___ subsurface mailing list subsurf

Re: we'll need to release a 5.0.7 pretty soon

Hi Dirk. Spanish strings are up to date right now. PR sent for the draft announcement. Best regards. Salva. El vie, 18 mar 2022 a las 17:22, Dirk Hohndel via subsurface (< subsurface@subsurface-divelog.org>) escribió: > I pushed a draft for the announcement (yay, this time I remembered to do >

Re: we'll need to release a 5.0.7 pretty soon

I pushed a draft for the announcement (yay, this time I remembered to do this BEFORE I release the version). Also pushed the latest translations that we have. A number of languages are missing the last few phrases. Of our more commonly used languages here are the top few that are almost complete

Re: we'll need to release a 5.0.7 pretty soon

> On Mar 17, 2022, at 10:04 AM, Robert Helling wrote: > > Hi Dirk, > >> On 17. Mar 2022, at 16:46, Dirk Hohndel via subsurface >> > > wrote: >> >> Ok, so admittedly, this is my fault. I wasn't paying attention to GitHub's >> announcements. >> Actual

Re: we'll need to release a 5.0.7 pretty soon

Hi Dirk, > On 17. Mar 2022, at 16:46, Dirk Hohndel via subsurface > wrote: > > Ok, so admittedly, this is my fault. I wasn't paying attention to GitHub's > announcements. > Actually, I don't recall ever really noticing the announcement. > But whatever - two days ago they turned off the git://

we'll need to release a 5.0.7 pretty soon

Ok, so admittedly, this is my fault. I wasn't paying attention to GitHub's announcements. Actually, I don't recall ever really noticing the announcement. But whatever - two days ago they turned off the git:// protocol for accessing their servers. And we used that in our submodule and in a few o