#apertus IRC Channel Logs

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

Hi, morning!

why screens?

yes, i have

as image buttons belong to button bar topic, it should be handled there

okay, i thought as x and y are the parameters of ImageButton so i can initialise them along the icon data

the home button is usually placed in the left button bar, which takes care of position

the button is still fixed in size, but now it's tied to the icon size, the goal is to have button of any size higher than the icon, like 200x100 and icon centered for now

yes, also the image button or image button with text could be placed at the bottom or top bar, and there it has to be wider

good day

hi

<BAndiT1983> what i see in the code additionally are attributes starting with capital letter, e.g. _X, this is not according to the guidelines <- what BAndiT1983 means is that there are certain naming conventions for variables and member fields, all members start with "_" and are follow by a lower case letter

okay, got it! thanks!

we should copy those guidelines to the remote readme

also an option CodingGuidelines.md ?

usually we shouldn'T have public attributes, as everything should happen through setter/getter

and the term is member variable or member field not "attribute" no?

variables in classes are called attributes

"The C++ standard, however, does not use these terms (apart from attributes of course, as explained above). If you don't want to risk anything and always be correct, use "data members" and "member functions"."

https://en.wikipedia.org/wiki/Member_variable

that's not C++ from microsoft, but the hybrid for .NET interoperation

haven't used their version for quite some time, as they have some properties there, which are not standard at all

am sticking to method and attribute, as that's what we use at work also

feel free to update, extend/improve: https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/CodingGuidelines.md

also added reference to readme: https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/README.md

the order in the guidelines has to be adjusted a bit, as naming is at the bottom, but can be done a bit later, have to do my regular work first

metal_dent[m]: any news?

should there be any constraint on the length of the makefile?

as i need to add the commands for the xbm to header file conversion so i was thinking maybe the makefile might look messy / long so i can make another script which is called from the makefile

alright! will be completed by today..

morning folks!

i kinda underestimated this task ':D, maybe it will take a little longer... sorry for that

wasn't a bloody mess last time I checked ... what happened? :)

> wasn't a bloody mess last time I checked ... what happened? :)

Bertl: was just a figurative speech, as the results are not that obvious when doing some things related to hardware, especially when you don't have that many output options, but USB-UART worked well

ohh sry, i thought Bertl asked me ':D

here -> https://pastebin.com/raw/Y6BzVx1N

ah, it's a script at the top

like the header file structure we have but without the data

.h files are created but the WIDTH, HEIGHT's values are blank

*execute in the terminal

https://unix.stackexchange.com/questions/283407/can-sed-save-its-output-to-a-file

and why not directly?

`sed -i "/data_icon\[/ s/1/$(WIDTH)/" $(1)`

because there are multiple places where width and height need to be placed

in the data[width*height] and also in the icon_name = {width, height, {data} }

inherit from Icon and try to do it manually first, to see if it is required to init it over multiple layers

why do you use 1 instead of placeholders? second thing, it's still not deriving from Icon, which provides generic structure

first you should add placeholders, otherwise i cannot recognize what you are replacing

okay, noted!

*-do +add

works glitch-free at 1080p60 with my monitor

hurray!, great anuejn!!!

with some tweaking it also seems to work with 2304×1440@60Hz (218.75Mhz pixel clock)

that is impressive!

didnt try (yet?) on the beta

even with the exact advertized modelines it doesnt work

are you generating RGB or YCrCb?

but should the monitor be able to detect what we are sending?

I've also had problems with the CamLink4K and any output from the Beta

I suspect that the firmware does check certain settings in the HDMI chip and/or the HDMI chip does check/require certain settings

ah ok i see

bc. i cant find it in the modeline

Display Type field bits 3-4 maybe?

https://edid.tv/edid/660/

good point

I2C registers should be available via USB

yup

let me dig out my notes ...

good to know