<OscarL>
ah... too late to give a WB! to phoudoin! (but let us hope we'll see him again soon :-D).
* OscarL
waves at scanty.
<scanty>
oh, hello OscarL!
<OscarL>
nice to read you scanty! Hope you're doing well :-)
<scanty>
sorry, was coding on another desktop.
<scanty>
i'm doing all right for the most part. having some issues with my special lady.
<OscarL>
Some things in life seem unavoidable :-/
<scanty>
eh, if it wasn't that, it would be something else.
<OscarL>
indeed, lol :-)
coolcoder613 has quit [Ping timeout: 480 seconds]
<OscarL>
In any case, always nice to hear you're busy coding.
<scanty>
thanks! i'm working on some tile stuff for my emulator
mmu_man has quit [Ping timeout: 480 seconds]
<scanty>
day off tomorrow... hope to make some more progress.
coolcoder613 has joined #haiku
<scanty>
i wish i had a big whiteboard that i could draw diagrams and charts for code.,
lovelytransgirl[m] has joined #haiku
<OscarL>
mmm, whiteboards can be nice. I remember making using them a lot (well... not actually whiteboards, but just some glass window) to try to explain my crazy ideas to co-workers :-D
<scanty>
all good code is a little crazy :)
<erysdren>
true lol
diver has quit [Quit: Leaving.]
HaikuUser has joined #haiku
SLema has joined #haiku
HaikuUser has quit []
meow has joined #haiku
meow has quit []
meow has joined #haiku
meow has quit [Remote host closed the connection]
meow has joined #haiku
<AlienSoldier>
OscarL not a bad idea to use a window for that, i often see free ones, does not even need to be insulated.
meow has quit []
<AlienSoldier>
Just need a coat of white paint on the side you don't write on.
<OscarL>
The window we used had a white background already (it "faced" an internal hallway), so just non-permanent markers were required :-)
<AlienSoldier>
tou need a permanent one for the very very important stuff :P
<AlienSoldier>
*you
<OscarL>
heh
<OscarL>
or for resignation messages :-)
<AlienSoldier>
that is funny!
HaikuUser has joined #haiku
HaikuUser is now known as xybre
<xybre>
Is there a way to render HVIF images larger than 64x64?
<OscarL>
not sure how the coordinates ranges mentioned there may affect rendering sizes.
<xybre>
Ideally the same way it scales down, proportionally, I'd think?
<xybre>
It looks like BitmapExporter can take any arbitrary size, the limitation is probably just the export menu
<scanty>
bedtime. good night.
<OscarL>
sleep well scanty! See you around!
<OscarL>
xybre: started my Haiku install, just to check... (I only ever use Tracker in List mode view)...
<OscarL>
Tracker allows to set "Window->Icon view->128x128", so at the very least hvif rendering can handle that.
<xybre>
Yeah it looks like EXPORT_MODE_BITMAP_64 in Icon-O-Matic just sets BitmapExporter(64). It should be pretty easy to hack in a larger value for export to PNG.
<OscarL>
xybre: Deskbar's "Preferences->Data Translation->HVIF icons" you can change the "render size" there too (for vector->raster ops)
<OscarL>
maxex out at 256.
<OscarL>
*maxes
<xybre>
Oh interesting, I would not have thought to look there
<OscarL>
My Atom N450 based netbook is officially battery-less now. Tried to replace the cells once again (worked fine a few years ago). No such luck this time.
<OscarL>
Guess the BMS board is fried/shorted because cells started overheating shortly after final assembly :-D
<xybre>
I'm potentially working on an HVIF viewer for other platforms and I found some other HVIF parsers/renderers but they all seem to struggle with some shapes and I wanted to generate a high res reference.
* OscarL
avoided setting his house on fire, somehow.
<xybre>
:o
<xybre>
The Data Translation setting does improve the quality of HVIFs loaded in ShowImage, fyi
<xybre>
Yeah, I was kinda avoiding that one because I didn't want to figure out how to compile VB.NET on Linux, but I do want to see if it renders better than Mauve's and Haikon
janking has joined #haiku
<janking>
hi
<OscarL>
Mmm, N450 netbook runs way too hot in Haiku. RAM is hot, even the miniPCIe WiFi card is hot :-/. Wonder if the motherboard is just dying or something :-(
<OscarL>
hello there janking.
<janking>
:)
<erysdren>
hi janking
linuxmaster has joined #haiku
<OscarL>
I mean... my Atom N450, Atom N2600, Phenom II X4 all run way too hot by the lack of P-State driver, but... this feels like too much :-)
<OscarL>
wonder what's the chance of adding an "acpi-cpufreq equivalent" driver into waddlesplash's contract wishlist :-)
<OscarL>
given that hvif2png links to libroot/libbe (even if the "_build" versions), writting your own custom build scripts will be far from trivial.
<xybre>
Oh there's a whole separate repo for buildtools, I thought I was losing my mind not being able to find the jam source
<xybre>
Okay, building jam was easy once I had the source. That's really cool. I am now the proud owner of hvif2png on Linux!
talos has quit [Ping timeout: 480 seconds]
<xybre>
It's interesting that the reference image isn't perfect when exported via hvif2png either. Much better than any others for sure. So the problem in this case is probably a minor error in the HVIF file itself.
<OscarL>
what are you using as the "gold standard"?
<xybre>
hvif2png now, as it is the reference implementation. I found a test pattern image on Sembience's file format samples and that is the file I have been testing with.
<xybre>
Mauve's implementation really struggles with curves. Haikon does pretty well but has some odd warping issues in a couple places..
<OscarL>
you said: "the reference image isn't perfect when exported [...]". I mean... compared to what? Tracker? Icon-o-Matic? Some pre-rendered image?
<OscarL>
(just curious, btw)
<xybre>
I mean the image itself is clearly incorrect, as a test pattern
<xybre>
The concentric circles don't quite line up for the top left target
<xybre>
The misalignment is (un)fortunately not visible at the resolution that Icon-O-Matic displays at. If you turn up the Data Translation option to max and then open it up on ShowImage you will see slight misalignment. The alignment becomes more obvious at higher resolutions.
<OscarL>
set size in DataTranslations to 256 and now I see what you mean.
<xybre>
It's probably the file rather than a rendering problem
<OscarL>
or just one of those pesky rounding errors :-)
<xybre>
Authoring highly accurate HVIFs is challenging
<xybre>
Hopefully with 24 bits of floating point resolution we won't see any at just 1024 but maybe!
<OscarL>
I only managed to create *one* .hvif. a green circle gradient with black border, so, hardly an expert here :-P
<xybre>
I've thought for years about using the HVIF format to store vector data. I have an allergy to SGML.
<OscarL>
.hvif is pretty sweet.
<OscarL>
(even from an end-user point of view)
<xybre>
In the end I might end up with an HVIF-extended format, on the off chance I run into a limitation, but I'd rather start with vanilla and go from there.
<xybre>
I like the single pass nature of it in particular
<OscarL>
Bet Stephan Aßmus would be glad to hear that people still like his work in 2025 :-)
janking has quit [Quit: Vision[]: i've been blurred!]
<OscarL>
/bin/query needs some form of parameter optimization. I get *wildly* different timings with:
<OscarL>
time query -e -v /Data1 "((name!="port.recipe")&&(name=="*.recipe"))"
<OscarL>
than with:
<OscarL>
time query -e -v /Data1 "((name=="*.recipe")&&(name!="port.recipe"))"
<OscarL>
~52s vs ~6s first run, 0.75s vs 0.2s on second run (nice speeds up on second run, though! :-D)
<OscarL>
(I ran the "fast version" first here)
<xybre>
Thanks for your help, both of you! I'm going to get some rest now :)
<nekobot>
• threedeyes (0fe3e7f8): tg_owt: bump for rebuild
<OscarL>
I need to add "-e" to all my query aliases because otherwise it breaks "ctrl+click" open from Terminal.
<OscarL>
(for filenames that need "escaping", like recipes that have "~" in their filenames)
<Begasus[m]>
I feel an update to telegram coming up :)
<OscarL>
was thinking the same :-D
<Begasus[m]>
pfew ... no mass email today :P
<OscarL>
Sorry. I was too bussy attempting to set my house on fire, apparently. :-D
<Begasus[m]>
next round on openSCAD waddlesplash :)
<erysdren>
OscarL: you okay man? lol
<Begasus[m]>
yeah read something just now, it's gone now?
<Begasus[m]>
Hi erysdren (@_oftc_erysdren:matrix.org)
<erysdren>
hi Begasus
<OscarL>
erysdren: yeah, all good. Just had a bit of a scare with some lithium cells :-)
<erysdren>
ahh scary!
<Begasus[m]>
time for coffee :) (fresh*)
<erysdren>
glad you're okay
<OscarL>
All good! Noticed the increse on temps, and managed to open the baterry enclosure and rip out some cables before it actually became ablaze :-D
<Begasus[m]>
had some luck there then !
<OscarL>
I just double checked my soldering work. No mixed up cables, so I guess the board just had a short circuit (and that was why previous cells died)
<OscarL>
Begasus[m]: indeed.
<OscarL>
Begasus[m]: now the only fire-hazard is the two bateries in parallel I have soldered and taped to the back of my "new" phone :-P
<Begasus[m]>
whoot! living the dangerous live there! :P
<OscarL>
I hate buying new stuff when old stuff can be repaired. Also... no money for new stuff anyway, so... win/win (with a slight chance of flames) :-P
<Begasus[m]>
error: 'const class QTime' has no member named 'elapsed'
<Begasus[m]>
this seems obsolete from before qt5? :P
janking has joined #haiku
<OscarL>
#include <QTimeTraveler.h>
<janking>
Good morning :)
<OscarL>
erysdren: just opened the qbrush-alphashadow.svg file you added for trenchbroom. Noice! kudos to your friend!
<erysdren>
i'd like it if we can add a credit or link-back to them somehow in the recipe
<erysdren>
any idea how we could do that?
<erysdren>
if possible...
<OscarL>
I guess nothing prevents you to add a line or two to the DESCRIPTION (as visible as it can get, I think)
<Begasus[m]>
you could add it to COPYRIGHT?
<erysdren>
might do that, and for QuakeSpasm too (they made the logo there too)
<OscarL>
other than that... links/mentions on the commit messages/PRs would be my go to.
<Begasus[m]>
and a co-authored-by in the commit message for the icon?
carlomon1e has quit [Quit: leaving]
* OscarL
wishes we would just get rid of COPYRIGHT.
<Begasus[m]>
can't remember when I actually used one of those screw type of connections :P
janking has quit [Quit: Vision[]: i've been blurred!]
<OscarL>
meanwhile I have one of those at arm's reach :-D
<Begasus[m]>
still nogo with that Qt error
<OscarL>
Those VGA connector are something else. On one hand... you wouldn't lose image with just a like kick on a cable. On the other hand... if you really trip over those cables (and the screws were secured)... both pc AND TV/Monitor would end up in the floor :-)
<nekobot>
• threedeyes (04e308e9): Telegram: bump version
<Begasus[m]>
there it is! 🎉
talos has joined #haiku
<Begasus[m]>
me feeling stupid :P used "qmake6" instead of just "qmake"
<OscarL>
If using QElapsedTimer instead of QTime would make it work with Qt6 (instead of Qt5)... I would consider patching it, even if just to see if it works :-)
<Begasus[m]>
the .pro file even mentions Qt4, so not going to patch the lot there :P