Current Server Time: 19:53 (Central Europe)

#apertus IRC Channel Logs

2020/06/14

Timezone: UTC


00:27
Bertl_oO
off to bed now ... have a good one everyone!
00:27
Bertl_oO
changed nick to: Bertl_zZ
01:05
calle__
joined the channel
01:08
mumptai_
left the channel
08:11
BAndiT1983|away
changed nick to: BAndiT1983
08:24
david[m]17
joined the channel
09:47
calle__
left the channel
09:48
mumptai
joined the channel
09:56
comradekingu
left the channel
10:02
comradekingu
joined the channel
10:45
ronald[m]
joined the channel
11:29
Bertl_zZ
changed nick to: Bertl
11:29
Bertl
morning folks!
11:29
BAndiT1983
hi
11:30
se6ast1an
good day
13:56
panintended
Hi all
13:56
panintended
BAndiT1983:
13:57
panintended
Regarding the Observer pattern, will the attributes that Observers subscribe to be static, or would you expect it to change during runtime?
13:58
BAndiT1983
hi panintended, how are you?
13:59
BAndiT1983
they will be static, as remote will only handle the ones which are available in the firmware
13:59
panintended
To clarify: would you expect the pool of attributes to change during runtime (attributes added/removed from the pool). their values are expected to change of course :)
14:00
BAndiT1983
later we can do something like request all available ones from the camera when remote starts
14:00
BAndiT1983
nah, not really, but maybe Bertl or se6ast1an have different ideas about that
14:01
panintended
I'm doing well, I'm afraid it's going just weekends for me for AXIOM from here on (better than nothing though). Yourself?
14:02
panintended
I see, thanks for the clarification!
14:02
panintended
I'm trying to cut down as much as I can on memory allocation/copying, and this just came to me :)#
14:02
BAndiT1983
trying to push things forward, but have to do some time management as private life also needs attention
14:03
panintended
of course :)
14:03
BAndiT1983
as long as you don't use new() ;)
14:04
panintended
really? no new()?! ;)
14:05
panintended
actually it was about copying over the C-strings in which attribute names would be stored in when an observer subscribes, etc. But it looks like that won't be necessary
14:06
BAndiT1983
would enum class help? but i think that we need to register things a bit dynamically, so maybe string would be ok
14:07
BAndiT1983
new() is possible, but it consumes additional memory and heap has to be adjusted in the linker, we know our requirements beforehand, that's why dynamic memory was ditched
14:08
panintended
yeah, and in general dynamic memory is not great for real-time systems
14:09
panintended
Well an enum would really simplify things, yes. If we're going with a static attribute pool, we might as well ditch strings completely
14:11
panintended
Do you mean something like enum Attribute { WHITE_BALANCE, EXPOSURE, <OTHER CAMERA CONFIG>, ... };
14:11
BAndiT1983
yep
14:12
BAndiT1983
but c++11 enum please, aka enum class
14:12
BAndiT1983
this would avoid collisions, naming schema is a bit different there, but you can also use the classic enum naming
14:14
panintended
ok, cool
14:14
panintended
thanks
14:16
BAndiT1983
no problem
15:00
BAndiT1983
changed nick to: BAndiT1983|away
17:02
Bertl
off for now ... bbl
17:02
Bertl
changed nick to: Bertl_oO
17:02
panintended
Hi BAndiT1983. I've pushed to my fork the framework for the observer pattern. Can you have a look? Be sure to pull from branch "feature_T1203"
17:03
panintended
I'll be out for an hour or two, so I'll check any comments after that. Thanks!
17:06
panintended
https://github.com/panintended/AXIOM-Remote/tree/feature_T1203
17:25
se6ast1an
<BAndiT1983> nah, not really, but maybe Bertl or se6ast1an have different ideas about that <- no different ideas from me, since the parameters are dictated by the hardware everything is really "set in stone" :)
17:25
se6ast1an
like the image sensor parameters
17:26
BAndiT1983|away
changed nick to: BAndiT1983
17:27
BAndiT1983
panintended: will try to free some time and check it at some point
17:27
se6ast1an
one thing we could discuss is how we could handle new hardware with the existing Remote in the future, like the upcoming AXIOM Micro R3 hardware - but for me a simple firmware upgrade for the remote is the answer which extends the static list where required
17:27
BAndiT1983
certain remote firmware version for certain hardware/firmware version of beta
17:28
se6ast1an
yeah or just the latest firmware is able to support the latest cameras
17:28
se6ast1an
and understands which camera it is connected to
17:30
BAndiT1983
should also work, but we should keep probable differences in mind and handle them accordingly, e.g. missing parameters on certain camera models
17:30
BAndiT1983
we should just try to follow a route which is flexible enough and adjust the handling later
17:33
se6ast1an
agreed
17:34
BAndiT1983
but the point with missing params is easily doable, if we can get the list of available params of the camera and disable unavailable entries, they can still be there but greyed out, or just not shown at all
17:39
se6ast1an
yes, my idea would be to show the name of the recognized connected camera somewhere and then only display the parameters that this model supports
17:49
BAndiT1983
already having a plan for some time how to test it without actual hardware, but the implementation has probably done by someone else, as i'm still not progressing that well with my tasks at the moment, as other things are coming in-between again and again
18:28
se6ast1an
fingers crossed
19:23
bluez_[m]
Hey Bertl! Please ping me once you are back... I have an issue I need to discuss...
20:26
BAndiT1983
changed nick to: BAndiT1983|away
21:04
BAndiT1983|away
changed nick to: BAndiT1983
21:06
BAndiT1983
changed nick to: BAndiT1983|away
22:05
LordVan
left the channel
22:17
LordVan
joined the channel
22:59
alexML
left the channel
23:06
bluez_[m]
<bluez_[m] "Hey Bertl! Please ping me once y"> okay i solved the issue ':D ....will discuss tomorrow... off to bed now...
23:08
alexML
joined the channel