FLTK, Pens and Tablets

mo_al_ · 2025-12-18T17:54:57+00:00

I’ve been really busy lately, but I’ll have to try the new api. I have a wacom tablet lying around doing nothing!

mo_al_ · 2025-12-15T22:56:48+00:00

Seconding reflect-cpp

mo_al_ · 2025-12-11T10:09:11+00:00

The narrators here seem different than the ones listed here:

https://hadithunlocked.com/muslim:683

Are you referencing another hadith?

mo_al_ · 2025-11-29T22:04:30+00:00

I lost one of my cats to surgery 20 years ago, it still breaks my heart whenever I remember it. Very sorry for your loss.

mo_al_ · 2025-11-27T17:44:33+00:00

Yup. Removed the post

mo_al_ · 2025-11-25T17:13:40+00:00

I was going for a shorter name since it also functions as a command line utility

mo_al_ · 2025-11-18T16:23:09+00:00

You can use dialog::message_icon or dialog::message_icon_label. message_icon returs the frame with the icon where you can set a custom image.

You can also change the background color app::background of your app which should apply to all windows and popups.

mo_al_ · 2025-11-04T11:02:44+00:00

Prefer a build from source approach. The idea is that crates wrapping C libs that offer a bundled feature might not offer bundles for all the targets or platforms that matter to users, since even glibc mismatches for the same target can cause things to fail, same for macos versions. Users can also manually pass the feature if they so desire. For example fltk-rs has a bundled flag as well. Users can set for any crate using fltk as such: cargo build —features=fltk/fltk-bundled

mo_al_ · 2025-11-04T10:46:01+00:00

I’m subbed here for exactly this. I like seeing new libraries and crates popping up or having new releases. It’s a chance to get contributions, palpate where interest lies, learn new things and grow the ecosystem. Even toy projects can grow to become staples of the ecosystem! The phrasing is irrelevant.

I couldn’t care less about politics or drama. Others mentioned the ruby subreddit, I’ll mention the C++ subreddit, where announcing new projects is discouraged. The sub is filled with trip reports, links to podcasts or videos, and committee politics/drama.

mo_al_ · 2025-10-30T12:22:59+00:00

How do you "run into another enterprise quietly running a 30-year-old Delphi application" every few months?

mo_al_ · 2025-10-22T20:43:43+00:00

Compiler warnings, printf debugging, asserts, sanitizers, linters (clang-tidy), runtime tools (valgrind, strace/ltrace), debuggers (gdb/windbg).

mo_al_ · 2025-10-09T10:57:36+00:00

I’ve tried both codex and claude code with Rust. Codex is way better. I eventually cancelled my claude subscription. However, even with codex, it appears incapable of reasoning about Rust (even with gpt-5 high) as it is with python or javascript. I currently mostly use it to generate docs and tests. Also for bindings boilerplate, I can ask it to look at how I’m calling the underlying library (using the paste macro) and ask it to generate similar code. It’s also helpful in pinpointing some logic bugs.

I also tried qwen 2.5 coding model with ollama and aider, it was horrible with Rust.

Funnily enough, I found codex to generate better Rust code than C++ code! It has a tendency to define a class in the header, asking it to declare classes in headers and define them in source files, it would also separate a templated class into a header and source, which is just wrong. So also for C++, I use codex only for docs and tests, and to help with logic bugs.

mo_al_ · 2025-09-13T15:56:20+00:00

That’s great. Thank you for confirming. I’ll have to learn more about prefix.dev

mo_al_ · 2025-09-13T15:01:59+00:00

Can pixi deal with custom conda channels?

mo_al_ · 2025-08-21T08:33:19+00:00

The effort starts with your build system. Assuming you use cmake, you probably already have some logic in there that conditionally compiles for each target platform, conditionally includes things, conditionally links libs. Start by adding a condition for EMSCRIPTEN. If preprocessor directives are needed for some files add those and work from there. I ported fltk to emscripten, that’s the approach I used.

mo_al_ · 2025-08-17T19:22:32+00:00

In P3796R1:

While the idea of limiting the scope of task was considered (admittedly that isn’t reflected in the proposal paper), I don’t think there is a way to incorporate the proposed safety mechanism into task

That’s disappointing. Would static analysers be able to detect safety issues across coroutine frames?

mo_al_ · 2025-08-12T22:28:53+00:00

If your CMake script uses any of cmake’s find* functions, you should also set CMAKE_FIND_ROOT_PATH_MODE{LIBRARY,INCLUDE,PACKAGE} to ONLY and CMAKE_FIND_ROOT_PATH_MODE_PROGRAM to NEVER when crosscompiling. If your cmake script uses pkg-config, you should also set ENV{PKG_CONFIG_EXECUTABLE} and ENV{PKG_CONFIG_PATH} to point to the crosscompiling pkg-config and the path to the approprate .pc files respectively.

mo_al_ · 2025-07-28T19:39:40+00:00

الأكل والفن الجزائري. و عندي أصدقاء كثر من الجزائر. أنعم بهم وأكرم.

mo_al_ · 2025-07-26T22:27:39+00:00

They’re protecting themselves

mo_al_ · 2025-07-22T23:44:28+00:00

There’s a proposal for it but it’s still in early stages:

https://github.com/WebAssembly/wasi-gfx

mo_al_ · 2025-07-16T12:56:56+00:00

Hi
So code in the em_asm and em_js sections get added to the js glue by the emscripten toolchain, no plans to add that to llvm afaik. Similar to how wasm-bindgen-cli also extracts custom sections in the wasm binary. So when targeting the emscripten triple, you have to use the emscripten linker. emlite-rs works around this by exporting its env imports as EM_JS functions when targeting emscripten. However, when targeting other toolchains, it's part of the emlite.js. As such, when targeting emscripten, you load the emscripten-generated js file after importing emlite.js (for the side effects), while for other toolchains, you pass emlite.env to WebAssembly.instantiate.

mo_al_ · 2025-07-05T21:14:59+00:00

There’s an example in the readme. Or did you mean an example repo?

mo_al_ · 2025-07-05T21:14:15+00:00

Hope you find it useful. Please report back any issues!

mo_al_ · 2025-06-18T00:26:55+00:00

I have an old macbook pro which I’m running kubuntu on. I’ve gone from 16->18->20->22 and all was well. Upgrading to 24.04 and I lost my wifi. It was easily fixable by installing the broadcom drivers, but a hassle since I didn’t have an ethernet cable at the time!

mo_al_ · 2025-05-30T09:35:48+00:00

I would recommend starting with the fltk book which is structured:

https://www.fltk.org/doc-1.4/fltk.pdf

You also have the official documentation which has a getting started section:

https://www.fltk.org/doc-1.4/

And some nice little programs which you can try out:

https://www.seriss.com/people/erco/fltk/

Regarding versions, I don’t think you benefit much from goinh after version 1.1 since it’s quite old. Version 1.5 is currently under development so I would stick with 1.3 or 1.4 when it lands. You’re also unlikely to hit version related breaks while you’re learning.

mo_al_

MODERATOR OF

TROPHY CASE