Dmitry

Well, in the calendar the block designates the originally scheduled time.. I guess I could display clocked time as part of the event label?

Ahh gotcha that makes sense. It's more of a logging activity then. This doesn't really fit into my workflow, but if you're interested in creating a PR, I would be...

> Unfortunately, I don't have the skills to make this happen. You're an Emacs user so I beg to differ 😄 > Besides, I have to say that I deactivated...

Rudimentary implementation of this in feature/react-calendar branch. One issue that I haven't been able to resolve yet is that I rely on scheduled/timestamped items first and THEN get their clocked...

Great question. It's not available yet, but I'm targeting this for next release. If you feel like hacking up the code, you can change https://github.com/dmitrym0/org-hyperscheduler/blob/main/calendar/index.js#L110 from `'week'` to `'day'`.

Thanks @japhir will take a look. It's a bit odd because it's worked before without the branch specifier.

> Alternatively, consider not hard-coding the filename and top-level heading. Yeah, #1 is tracking this. > Instead, consider using [org-protocol-capture](https://orgmode.org/worg/org-contrib/org-protocol.html) to schedule a new event. This will simplify how users...

> Alternatively, consider not hard-coding the filename and top-level heading. #1 is fixed, available in the latest release. I will look into org-capture-protocol further though.

This is implemented in another branch.

I'm having trouble wit this as well. After reading #3, I reset the controller per the [manual](https://cdn.linak.com/-/media/files/user-manual-source/en/deskline-dpg-desk-panels-and-desk-control-app-user-manual-eng.pdf) and re-paired it. But it only seems to be reading the status and...