Current Server Time: 23:23 (Central Europe)

#apertus IRC Channel Logs

2020/04/23

Timezone: UTC


01:06
Spirit532
left the channel
01:06
Spirit532
joined the channel
01:36
Spirit532
left the channel
01:39
Spirit532
joined the channel
02:30
futarisIRCcloud
left the channel
02:47
Bertl_oO
off to bed now ... have a good one everyone!
02:47
Bertl_oO
changed nick to: Bertl_zZ
03:02
Guest25416
left the channel
03:04
Bertl_zZ
left the channel
03:04
Bertl_zZ
joined the channel
03:06
rahul
joined the channel
03:07
rahul
changed nick to: Guest80588
03:43
mumptai_
joined the channel
03:47
mumptai
left the channel
06:26
BAndiT1983|away
changed nick to: BAndiT1983
07:44
se6ast1an
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
07:49
BAndiT1983
se6ast1an: can you give a bit more background, as i only remember something very vague about this topic
07:50
se6ast1an
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.
07:50
se6ast1an
For many makers and small companies, this is a prohibitive amount of money, and forces them to resort to workarounds, such as using other organisations’ VIDs without permission, or simply making up a VID and PID. These solutions make things worse for everyone, by damaging the assumption that a VID/PID combination is unique to a given device.
07:50
se6ast1an
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.
07:50
se6ast1an
pid.codes is a website - weird TLD yes :)
07:51
BAndiT1983
thanks for the info
08:32
futarisIRCcloud
joined the channel
08:45
mumptai_
left the channel
09:24
BAndiT1983
changed nick to: BAndiT1983|away
09:36
BAndiT1983|away
changed nick to: BAndiT1983
10:04
mumptai
joined the channel
10:29
Bertl_zZ
changed nick to: Bertl
10:29
Bertl
morning folks!
10:52
se6ast1an
good day
12:38
vup
se6ast1an: maybe you should also update the link from axiom-beta-firmware to axiom-firmware (as we renamed them recently)
12:39
se6ast1an
ah yes, that has potentially created some dead links now
12:39
se6ast1an
did you find a particular place with 4040 now?
12:39
vup
se6ast1an: i meant in the pid.codes PR
12:39
vup
https://github.com/pidcodes/pidcodes.github.com/pull/494/commits/be01308f4bb4bd2ecbd978e3302782c7e26dcd24#diff-e17e0ea2bda20f13f0e2f4dd90df5a68R7
12:39
se6ast1an
ah, right!
12:40
vup
github redirects the old repo to the new one, so all links should be fine for now
12:41
se6ast1an
done
12:41
vup
great
12:48
metal_dent[m]
Hi, when you click on WB option, does the "Whitebalance" title is shown properly?
12:53
se6ast1an
hi metal_dent[m] - are you asking about the font size?
12:54
metal_dent[m]
yes sort of, as the text is only half visible
12:55
se6ast1an
yes, I also see its too big
12:56
se6ast1an
please choose a smaller font size: https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/Firmware/UI/Screens/WhiteBalanceScreen.cpp#L41
12:56
se6ast1an
I still have the debug painter enabled so my fonts are all the wrong size due to: https://lab.apertus.org/T1175
13:07
metal_dent[m]
> please choose a smaller font size: https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/Firmware/UI/Screens/WhiteBalanceScreen.cpp#L41
13:07
metal_dent[m]
done!
13:16
metal_dent[m]
um.. shouldn't it be "white balance" and not "whitebalance"?
13:16
se6ast1an
good point, yes "White Balance"
13:17
metal_dent[m]
okay, will correct that too :D
14:11
illwieckz
left the channel
14:11
BAndiT1983
am onto fixing the debug painter, just need to evaluate proper way
14:15
illwieckz
joined the channel
14:17
metal_dent[m]
Have you managed to narrow down the problem?
14:20
BAndiT1983
yes, painter is duplicated in memory and i have to resolve this, so there is only 1 painter, maybe not decorator pattern, as we don't have some partial interface, but strategy pattern which applies to the 2 methods which need overlay
14:20
BAndiT1983
currently evaluating what would be less invasive way to override individual methods and to use same painter
14:23
se6ast1an
pr merged, thanks metal_dent[m]!
14:24
se6ast1an
github is very slow currently, not sure it went through...
14:24
metal_dent[m]
se6ast1an: thanks!
15:19
se6ast1an
BAndiT1983: is this PR still relevant?
15:19
se6ast1an
https://github.com/apertus-open-source-cinema/AXIOM-Remote/pull/5/commits/8a4b06d0d5e2b18edb597fd3a46846df36a8399b
15:29
BAndiT1983
yes
15:29
BAndiT1983
it seems like many people are having trouble to find pic32 compiler
15:30
BAndiT1983
build is failing, maybe it has to do with slow github you've mentioned
15:47
se6ast1an
right, so I will mege the pr
15:47
se6ast1an
*merge
15:47
se6ast1an
ah I cant
15:47
se6ast1an
"supragya requested a review from BAndiT1983 on 23 Feb"
15:47
se6ast1an
This pull request is still a work in progress
15:47
se6ast1an
Draft pull requests cannot be merged.
15:50
BAndiT1983
have approved
15:51
se6ast1an
great
15:51
BAndiT1983
merged
16:09
metal_dent[m]
is the idea behind the "Debug Overlay" slider is to get into debug mode directly?
16:11
se6ast1an
I guess the idea is that you can turn the debug painter on/off, but its expected not working yet
16:11
metal_dent[m]
alright
16:13
BAndiT1983
yep, but calling it debug mode is mislead
16:13
BAndiT1983
*misleading
16:13
BAndiT1983
off for a moment
16:14
BAndiT1983
changed nick to: BAndiT1983|away
16:14
metal_dent[m]
yeah, I meant debug painter ':D
16:20
metal_dent[m]
what do button_up and button_down mean?
16:21
se6ast1an
when a physical button on the remote is pressed there are two events
16:21
se6ast1an
pressing it down
16:21
se6ast1an
and releasing it afterwards
16:22
se6ast1an
normal actions are only executed on the release event
16:22
se6ast1an
but the down event should set buttons on the screen to be highlighted
16:24
comradekingu
left the channel
16:26
metal_dent[m]
oh okay!
16:28
comradekingu
joined the channel
17:11
mumptai_
joined the channel
17:14
mumptai
left the channel
18:19
BAndiT1983|away
changed nick to: BAndiT1983
18:22
BAndiT1983
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
18:23
BAndiT1983
every new definition, if we would extend it in the future, would only need to cover specific element and not the actions
18:25
metal_dent[m]
okay :/
18:27
metal_dent[m]
I'm trying to implement the home button, but it's not working yet :/
18:27
BAndiT1983
which hime button?
18:27
BAndiT1983
*home
18:28
metal_dent[m]
the "home" button on the visualizer..
18:28
BAndiT1983
are you talking about "button up" or side bar?
18:28
metal_dent[m]
sidebar
18:29
BAndiT1983
the button bar example should have everything you need, in fact you should use the button bar for the side bar
18:31
metal_dent[m]
yes, I did what you have done for the "Cancel" button
18:32
BAndiT1983
have you set up debugging? this would help you to check where the application is jumping to
18:33
metal_dent[m]
not yet
18:33
BAndiT1983
will investigate at some point, how much space pure virtual methods are taking, but trying to avoid them usually, as i know that the compilers for microcontrollers are not optimized there, or at least weren'T a couple of years ago
18:33
metal_dent[m]
and I have one more question:
18:33
BAndiT1983
you should, as it's mandatory for proper development
18:34
se6ast1an
I should also set up the debugger for visualizer, with vscode?
18:34
metal_dent[m]
can't we implement the home button directly in the MainPage.cpp? like "SetCurrentScreen(main)" ?
18:34
BAndiT1983
to check when problems are there, yes
18:35
BAndiT1983
all the buttons will have handlers, so the logic is not bound that tight
18:36
BAndiT1983
nope, not in MainPage, the home button should be in the base class, as it will show up on most screens, except MainPage(!!!)
18:36
metal_dent[m]
ohkay
18:38
metal_dent[m]
i didnt know that and i was drawing it on the mainpage ':D
18:39
BAndiT1983
this is a very rigid approach, please look up loose coupling in software development and why it's my target for the firmware and bootloader
18:41
metal_dent[m]
alright
19:03
BAndiT1983
launch.json for debugging -> https://pastebin.com/raw/9nJ58neg
19:04
BAndiT1983
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
19:05
metal_dent[m]
BAndiT1983: needed it, thanks!!!
19:06
BAndiT1983
this setup is specific for vscode, if you use VI then you have to ask Bertl
19:06
BAndiT1983
if you press F5, it would present you some options, it's not hard to set up, but special setups can be a bit of headache
19:07
metal_dent[m]
no switched to vscode yesterday for debugging ':D
19:08
BAndiT1983
this will result in 'dislike' from Bertl on your facebook page
19:09
metal_dent[m]
dont worry, still use vim for coding XD
19:11
metal_dent[m]
trying to get a balance between you both ;)
19:12
BAndiT1983
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
19:14
metal_dent[m]
> launch.json for debugging -> https://pastebin.com/raw/9nJ58neg
19:14
metal_dent[m]
after this any other change..?
19:15
BAndiT1983
it depends on your environment, try it and see if it helps
19:26
metal_dent[m]
it worked, thanks! but will do the debugging tomorrow
19:26
metal_dent[m]
off to bed now, good night!
19:32
BAndiT1983
good night
19:36
calle__
joined the channel
19:37
mumptai_
left the channel
19:40
calle__
left the channel
22:44
BAndiT1983
changed nick to: BAndiT1983|away
23:44
illwieckz
left the channel
00:37
illwieckz
joined the channel