Mitchell Dalvi Rosen

An update: ``` stack build --flag fltkhs:bundled stack exec fltkhs-light-theme-skeleton ``` does work, but ``` cabal new-build --constraint="fltkhs +bundled" ``` does not seem to find the patched `freetype-config` during `configure`:...

`new-build` does download and install the package; it's a bit like old-install and old-build at once. Here's the full build log. Expand ``` File monitor 'config' unchanged. this build was...

@sboosali Yeah, I tried with this `cabal.project` as well: ``` packages: . package fltkhs flags: +bundled ```

I see... I'm still having some difficulty understanding. Which call is which? I'm not entirely clear on what `BaseButton` is, and the source you linked also mentions `DerivedButton`. However, neither...

I read over the docs a bit more and I'm starting to understand. My understanding now is that in `fltkhs`, `FooBase` _is_ `Fl_Foo`. The non-`Base` versions have no analogous class...

Interesting! A follow-up question, if I were to write my own `Button`, would I subclass like this? ``` WidgetBase -> Widget | v ButtonBase -> Button -> MyButton ``` Or...

Got it. Another question (sorry!) - the `*Base` types do crop up in the API, for example in ```haskell getParent :: Ref WidgetBase -> IO (Maybe (Ref GroupBase)) ``` you're...

Very helpful! Could you clarify why one might not want to immediately upcast every `Foo` they encounter to a `BaseFoo`? I'm still struggling to understand the essence of the distinction...

Oh - is the answer that in doing so, you'd toss out your custom overrides?

Bump, I'm still interested in this :) Any blockers for this moving forward @HuwCampbell?