Doesn't this just boil down to migrating from the cloud to leased servers?
The whole FreeBSD, jails etc could've just been any form of containerization on linux and the result would've been the same.
You can use dynamic_cast instead of reinterpret_cast. If the pointer isn't correct it would return null. A better solution is to subclass the widget, store a function pointer for the callback which takes the same class instead of an Fl_Widget, and call that in the callback:
https://github.com/MoAlyousef/FLMH
This uses a std::function for the captures but you can use a function pointer as well.
Doctor-patient written communications (email, whatsapp whatever) can put doctors in legal risk whether they answer or not. Answering in a meaningful way also takes from the physician's time, much of it during their after-hours.
The clinic where I practice requires making a telephone number and email available to patients. A lot of patients might use them sensibly but some patients just abuse this.
If it were up to me, I would also put a cost on each form of communication as if it were a visit to the office!
> The clinic where I practice requires making a telephone number and email available to patients
I wonder if contacting your doctor directly is a US thing? Before this discussion I had never heard of such an option. I definitely don't have any way of directly contacting any medical staff, neither a nurse nor a doctor, it will have to be through an appointment.
This might finally explain why this "ask your doctor" is so often repeated online as a realistic option? You definitely won't ask your doctor about every minor thing if it's behind an appointment.
Actually FLTK has full unicode support, right-to-left and bidi text.
The limiting factor is the OS.
For rtl and bidi, it depends on the OS. On linux for example, if FLTK is built with pango support, it'll support them just fine. On windows and macos, these work out of the box.
As for accessibility, the only thing missing is screen reader support. Otherwise tab navigation, ime and other modalities are supported.
FLTK's bindings in Rust provide an accesskit adapter which supports screen readers using the accesskit crate.
