-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't draw a Button? #109
Comments
Direct calls to That said if |
Thanks for the tips, I'm just messing around with wrapping this library in a more haddock-friendly / idiomatic way, I'm not actually drawing buttons just yet :) |
@mitchellwrosen could you ping me if you release such a package? i also want to write my own wrappers over an FLTKHS subset (for my personal applications). |
@sboosali Sure, you can follow my progress here https://github.com/mitchellwrosen/fltkhs-simple It's really nothing special, my idea is to simply use concrete newtypes around refs, and to wrap/re-expose their entire APIs (including all parent types) individually. There are probably lots of reasons why I would not want to do this, but I'm just trying to learn the API at the moment, and wrapping helps with that. |
thanks!
…On Mon, Apr 22, 2019, 14:01 Mitchell Rosen ***@***.***> wrote:
@sboosali <https://github.com/sboosali> Sure, you can follow my progress
here https://github.com/mitchellwrosen/fltkhs-simple
It's really nothing special, my idea is to simply use concrete newtypes
around refs, and to wrap/re-expose their entire APIs (including all parent
types) individually. There are probably lots of reasons why I would not
want to do this, but I'm just trying to learn the API at the moment, and
wrapping helps with that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#109 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AARWQMLKV6U3HXT2AKEGYRLPRYRR3ANCNFSM4HHRKJNQ>
.
|
Calling
draw
on aRef Button
is a type error:However, it seems like it should be able to, per the hierarchy
Base.Widget -> Base.Button
The text was updated successfully, but these errors were encountered: