#apertus IRC Channel Logs

off to bed now ... have a good one everyone!

small update from the pid.codes front: maintainer went through all PRs now and asked for a single URL to be supplied pointing to sources (I added one for software and one for hardware) -> reduced it to only software now in our PR

If you’re a maker, hobbyist, or startup company producing your own USB device, you’ve probably discovered that you need a USB Vendor ID and Product ID to uniquely identify your device to computers. The USB-IF’s position is that the only way to do this is for each organisation to pay $5000 for a unique Vendor ID, which they may not share with other individuals or organisations.

pid.codes seeks to solve this issue for anyone producing open-source hardware. We have been gifted a Vendor ID by a company that was issued one by USB-IF and has since ceased trading; they obtained the Vendor ID before the USB-IF changed their licensing terms to prohibit transfers or subassignments.

thanks for the info

good day

ah yes, that has potentially created some dead links now

se6ast1an: i meant in the pid.codes PR

ah, right!

done

Hi, when you click on WB option, does the "Whitebalance" title is shown properly?

yes sort of, as the text is only half visible

please choose a smaller font size: https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/Firmware/UI/Screens/WhiteBalanceScreen.cpp#L41

> please choose a smaller font size: https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/Firmware/UI/Screens/WhiteBalanceScreen.cpp#L41

um.. shouldn't it be "white balance" and not "whitebalance"?

okay, will correct that too :D

am onto fixing the debug painter, just need to evaluate proper way

Have you managed to narrow down the problem?

currently evaluating what would be less invasive way to override individual methods and to use same painter

github is very slow currently, not sure it went through...

BAndiT1983: is this PR still relevant?

yes

build is failing, maybe it has to do with slow github you've mentioned

*merge

"supragya requested a review from BAndiT1983 on 23 Feb"

Draft pull requests cannot be merged.

great

is the idea behind the "Debug Overlay" slider is to get into debug mode directly?

alright

*misleading

what do button_up and button_down mean?

pressing it down

normal actions are only executed on the release event

the button state has to be stored first, as imgui only has immediate mode, then the current state has to be compared old state and if previous was down, now up, then "button up" should be sent and vice versa, don't know if it wouldn't be better to have like button IDs and their current state in separate enums, as knob can also be clicked

okay :/

which hime button?

the "home" button on the visualizer..

sidebar

yes, I did what you have done for the "Cancel" button

not yet

and I have one more question:

I should also set up the debugger for visualizer, with vscode?

to check when problems are there, yes

nope, not in MainPage, the home button should be in the base class, as it will show up on most screens, except MainPage(!!!)

i didnt know that and i was drawing it on the mainpage ':D

alright

i would advise to install cmake plugin also, it would recognize the cmake script automatically and one can select several options in the status bar, they would appear on the left side there, after the plugin is installed

this setup is specific for vscode, if you use VI then you have to ask Bertl

no switched to vscode yesterday for debugging ':D

dont worry, still use vim for coding XD

no need to do a balancing act, just set the environment up, how you would feel comfortable to work with, like i said before: have found my way of working after years of trying things out, so i know my tools and can work with them efficiently

after this any other change..?

it worked, thanks! but will do the debugging tomorrow

good night