Alexander Orlov

@0xceed
3 Followers
14 Following
25 Posts
Software Engineer. Swift, C and Rust. iOS and macOS mostly.
Developer of @discrete — music player for Jellyfin.
Matrix@0xceed:matrix.org
Discord0xceed
@grishka from what I’ve seen, they appeal to visibility by ISP, which in case of torrenting licensed media could and will result in legal prosecution. Which in some countries may end up even with real cell.
@grishka I think dark room and closing your eyes for a moment to ‘reset’ previous colour somewhat helps. Did 0.0025 first time and around this with consequent ones.
@grishka they don’t have business in ad industry, but quite actively forcing on point of ‘privacy’ for last decades.
@grishka almost forgot… if your custom view ONLY draws bitmap, maybe use NSImageView then? And update it’s image property — it’ll do same thing i described + optimisations.
@grishka well same thing you can do with bitmap. Your `draw` method will be drawing just bitmap on context than.
@grishka you don’t need display link for it actually. decoder have new data -> set it into view -> call needsDisplay -> `draw` called by system.

@grishka Consider drawing data directly into view’s context, not bitmap at least.

1. New data comes.
2. Gets analysed and mapped into comfy numbers for drawing.
3. Switch to main thread, set it onto your custom view.
4. While on main thread, set needsDisplay on that custom view.
5. When appropriate, you `draw` method will be called in custom view. There you just take comfy numbers and draw directly on context.

@grishka for future: if you render graph to bitmap, it usually goes with drawing on context from view directly or using core animation and layers.
@grishka if custom view which is rendering your bitmap is coded right (see image from LLM), that should be it.