#apertus IRC Channel Logs

hello, i am getting my internet repaired tomorrow so i'm not sure if i'll be at the meeting

tpw_rules: sounds great

off for now ... bbl

hey, I will report now, as I will be afk in a few minutes

after some consulting with vup, we decided that widgets should be able to spawn threads / async tasks and comunicate via event queues in one directiono and by modifying the existing listenables in the other direction

better wording: the side effects of the elm programming language

I then began to implement this concept

thats it from my side

many thanks anuejn!

*eppisai is here

tpw_rules reported his internet might be off now

Yes..

Last week, we tried to see why my remote hardware was not working, the mini module had died..

It will arrive in a day or two here..

And after trying remote was working (button part commented for now, until I flash the pic16s with mini module )

So, currently

1. It's not crashing

I finish the code properly and open a pull Request so code can be reviewed..

very good, you mentioned you also fill/clear the backbuffer now right?

Let me share the video here

From apertus-gsoc

*displayed

great, thanks! anything else to share?

*screen = menu, pause the video and use . and , to walk frame-wise through the process

does the 'sliding' animation make use of the LCD controller hardware sliding feature?

was that too complicated or too LCD specific?

Bertl: have started to investigate there, but something else has gotten in-between (new job)

vnksnkr: please go ahead

So I was finally able to get past the problems I had with the hardware

Which means I can use the python scripts for communication now after uploading the bitstream via the driver

I've been spending remaining time debugging my code, thanks to vup and Bertl for the livestream :) ..has been a great help

sounds good!

BAndiT1983 has some 3d remote news!

so called 3d remote, although we should find better name: https://lab.apertus.org/T1178

it's basically uses emscripten to transpile the firmware code to WebAssembly and JS, afterwards the framebuffer data is used in a webpage which uses three.js, so basically the code base was stripped out of the prototype for the 3d cad viewer, we've introduced some time ago

code is not uploaded yet, some cleanup is required and also binding for the real firmware code, at the moment it uses a bit modified one, where i'Ve removed some initializations, e.g. USB device, after cleanup is there and also CI build, it will be committed and anybody who has interest can play around or extend it

many thanks

just a basic setup and a bit of normal map for knurling, will supply the textures too (generated in substance designer)

technical university meeting is still on as well when manfred is back from the olympics in tokio at the end of august most likely

anyone else who wants to report/share?

thanks ...

we *non apertus related)

and we also investigated and mostly fixed some issues on the remote betas

that's it from my side

yay

ok anyone else with topics or additions?

Hello everyone :)

a little to report this week...Last week I had the channels communicating with the parallel interface ready and the training was successful

I added signals (frame_req, t_exp1...) to simulate the acquisition phase but the channels apparently stay in the IDLE mode

unlike before where the channels actually sent the data, but they weren't captured properly

that's it for me :)