On 6 Jan 2022, at 13:41, ed.vigmond wrote:
> 
> I was just wondering because I figured with all the WMs supported, it might not be too hard to add one which was a dummy and basically ignored events. 

The crux here is that “all” WM’s are “the same” in that they handle Window decoration and placement, and handle the events to/from the app. This is literally true under X11 where the Wm’s are more or less compliant with the ICCCM rules, and the Win32 and macOS systems are “analogous” to that, at least sufficiently that we can pretty much map the same logic and functionality in each case.

I suppose you could write a “dummy” WM-like stub that pretended to be implementing the ICCCM but did not actually communicate with any underlying X-server or such, but... Hmm, well, I’m not sure, actually... might be trickier than I initially thought... something like nano-X might be easier?
FWIW, the last time I tried nano-X (which was a while ago) it did work OK with fltk, though it took a little bit of poking - ISTR that I wrote up a HowTo at the time, so it’ll be on the fltk site somewhere, but... probably not that useful to you either, TBH.


> Anyways, the main issue was that I was on a cluster without a working Xvfb which has since been fixed.

OK, good.

> 
> 15+ years and 1000's of lines into developing my program, I probably would have done things differently if I had known.


Yeah. Hindsight...


-- 
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/9397ED61-8319-415A-B84F-4DA67660A3DC%40gmail.com.