<Not>
[haikuports/haikuports] Begasus 84eb93b - gerbera, bump version (#6902)
<Begasus>
let's squize this in :)
repetitivestrain has quit [Quit: Vision[]: i've been blurred!]
repetitivestrain has joined #haiku
<Begasus>
What size is int with x86_gcc2h? Just looking at libtiff's CMakeLists.txt line 304, seems it has decided that sizeof(int) != 4 and using long instead (which conflicts with GDAL's code which has it as an int).
<Begasus>
A question for the PR for gdal, I don't know there :)
<Not>
[haikuports/haikuports] jmairboeck 96f4955 - new recipe: python-ly (#6868)
ivanholmes has joined #haiku
<ivanholmes>
@waddlesplash: hi, r.e. our discussion on github - this driverdata field is a pointer
<waddlesplash>
indeed.
<ivanholmes>
so we need to create a data structure containing _window_map and _current_context for it to point to?
<waddlesplash>
AFAICT it's a generic way to store arbitrary data in the "driver", which is what we are (this is the Haiku driver)
<waddlesplash>
yes, I believe so.
<waddlesplash>
The first thing to determine is where driverdata gets allocated
<waddlesplash>
So, grep around the other drivers to see where they create/delete it
<ivanholmes>
Alright thanks I will do
Vidrep_64 has joined #haiku
HaikuUser has joined #haiku
<ivanholmes>
For reference my experience with programming is mostly embedded software/C so I know about some low-level stuff but I'm new to C++
<waddlesplash>
ah, OK
HaikuUser has quit []
<waddlesplash>
ivanholmes: appears we should be setting it up in HAIKU_CreateDevice and tearing down in HAIKU_DeleteDevice
<ivanholmes>
yeah other ports corroborate that from what I saw
<waddlesplash>
I would create a struct HaikuDriverData { } and make the things members of that
<waddlesplash>
then "new HaikuDriverData", set the pointer, etc.
<ivanholmes>
yes it seems there is an SDL_VideoData struct defined in headers for each port
<waddlesplash>
and then cast back in _DeleteDevice and "delete" it
<waddlesplash>
oh, is there a type?
<ivanholmes>
I think so?
<ivanholmes>
From pandora port: typedef struct SDL_VideoData { SDL_bool egl_initialized; /* OpenGL ES device initialization status */ EGLDisplay egl_display; /* OpenGL ES display connection */ uint32_t egl_refcount; /* OpenGL ES reference count */ uint32_t swapinterval; /* OpenGL ES default swap interval */ } SDL_VideoData;
<waddlesplash>
indeed
<waddlesplash>
good, then that means we don't need to do weird casting
<ivanholmes>
sorry for the horrible mess but that illustrates my point ha
<ivanholmes>
yep good
<waddlesplash>
this should be a C++ structure, so you can put the things in there
<waddlesplash>
you then need to use new/delete to create/destroy it
<waddlesplash>
You can also make the BApplication member functions part of this
<ivanholmes>
alright and using a C++ struct gets around the issue of putting a vector into a struct I suppose?
<waddlesplash>
well all structs in C++ mode are C++ structs :)
<waddlesplash>
you can put C++ types wherever you want. but if you put C++ types in a struct then you MUST use new/delete in order to make sure that member variable constructors are called
<augiedoggie>
waddlesplash: i thought about it but was just giving anyone a chance to object, i don't like python recipes
<waddlesplash>
augiedoggie: I don't either
<waddlesplash>
but, well, I have spent basically no time trying to find ways to improve them
<ivanholmes>
waddlesplash: right I see what you are getting at now, thanks
<augiedoggie>
:P
xet7 has quit [Remote host closed the connection]
x10z has joined #haiku
matt1 has joined #haiku
<matt1>
hello,
<matt1>
am i ok ?
<matt1>
have i to do something for you to go ok ?
<matt1>
;0)
Vitto has joined #haiku
<matt1>
my last girl = sorana iliescu from bucarest ...
<waddlesplash>
matt1: this isn't appropriate content for this channel.
matt1 has left #haiku [#haiku]
Vitto has quit [Read error: No route to host]
Vitto has joined #haiku
<Begasus>
hi ivanholmes !
<ivanholmes>
Begasus: hello :)
Begasus_32 has quit [Quit: Vision[]: i've been blurred!]
<Begasus>
Glad to see you made it to IRC :)
<ivanholmes>
cheers, a bit easier than github issues for quick questions or whatever of course
<ivanholmes>
never really used IRC before but seems there isn't that much to it
<Begasus>
Right, and keeps commenting on PR's a bit lower on email traffic :)
<ivanholmes>
quite, I think our thread on mupdf went over 100 messages ha
<Begasus>
heh
<Begasus>
If Charlie was around he would have complained already ;)
<ivanholmes>
who is Charlie? shows how new I am...
<waddlesplash>
heh, don't worry too much about being "new"
<Begasus>
Long time BeOS fan, and one of the guys behind BG (BeGeistert)
<waddlesplash>
even I'm "new" compared to Begasus, I think he's been around since the BeOS days, i.e. before I even existed
<waddlesplash>
:p
<Begasus>
ivanholmes, you know more about coding then me (which isn't that hard) :)
<ivanholmes>
well I have known about Haiku for years, lurking and trying it out on and off, most recent time I was very impressed and I thought I could probably help out
<ivanholmes>
ha I am also a post-BeOS individual
<Begasus>
Really appreciate it ivanholmes !
<ivanholmes>
Begasus: well thank you - I still have a lot to learn about haikuporter though ;)
<Begasus>
I know my way around recipes (and mostly check out PR's on 32bit), but when it comes to coding ... :)
<ivanholmes>
it's really no problem - Haiku is pretty much what I want out of an OS after all
<Begasus>
Nice to hear, a lot of people have been around since BeOS R5 (or earlier), a lot new ones
<ivanholmes>
ah yeah
<ivanholmes>
it seems to be an exciting time for Haiku anyway
<ivanholmes>
lots of progress over the last few years
<Begasus>
It's been a fun ride almost 20 years
<Begasus>
posted a screenshot from the early days (OBOS) before it came to known Haiku a while ago
<ivanholmes>
on discuss? or somewhere else?
<Begasus>
BeOS was spot-on the first time I tried BeOS R5 Pe
<ivanholmes>
by the time I tried it out as a kid it had already been abandonware for 10 years but remember liking it straight away
<Begasus>
Compared to SuSE/RH at that time it was a joy
<ivanholmes>
ha, nice
<ivanholmes>
yeah i bet, linux still sucks to this day of course
<ivanholmes>
not that it isn't powerful/useful/better than alternatives
<Begasus>
well, this laptop runs Ubuntu, mainly for checking out repology/email/google ...
<ivanholmes>
I use debian on my other laptop and my workstation
<Begasus>
now I have another laptop able to boot 32bit/64bit native through an external drive
<ivanholmes>
ah nice
<ivanholmes>
i was fortunate to already have an X230, used to run hackintosh on it but then I got a new Mac mini (dedicated to music stuff) because Apple keep messing up macOS
<ivanholmes>
got more and more annoying to use so I thought better to compartmentalise it
<Begasus>
yeah, some things passed by on the forum about that too
<Begasus>
but heading down here now, still on sick leave (hence the free time), but downside is that I can't stand the pain in the evening
<ivanholmes>
about apple silicon? or just the general state of mac as a platform
<Begasus>
as a platform
<ivanholmes>
ah that's a shame, hope you feel better soon
<ivanholmes>
ah right yeah
<Begasus>
same here ivanholmes thanks :)
<Begasus>
heading down here, g'night peeps!
Begasus has quit [Quit: Leaving]
<ivanholmes>
waddlesplash: i've moved the functions we talked about on github into the new SDL_VideoData struct, not sure how to call them from SDL_BApp.h though?
tqh has joined #haiku
Andros has quit [Remote host closed the connection]
<waddlesplash>
you don't
<waddlesplash>
they should be called directly from whatever needs them
<ivanholmes>
right but there is a MessageReceived implementation
<waddlesplash>
ah
<ivanholmes>
and some of the handlers for that need to call these functins
<waddlesplash>
well, then the SDLBApp should store a pointer to the SDL_VideoData
<waddlesplash>
probably it needs to be passed in to the constructor
Vidrep_64 has quit [Quit: Vision[]: i've been blurred!]
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
BrunoSpr has joined #haiku
<ivanholmes>
waddlesplash: you may have been notified anyway but I've just pushed my progress. it doesn't work (builds but crashes when trying to start opengl), wondering if I am generally on the right track
_Dario_ has quit [Quit: Vision[]: i've been blurred!]
bbjimmy has joined #haiku
_Dario_ has joined #haiku
* ivanholmes
is idle: must eat
ClaudioM has quit [Quit: leaving]
x10z has joined #haiku
<waddlesplash>
ivanholmes: post the crash report somewhere
<ermo[m]>
PulkoMandy: How available are you re. thinking about keyboard patches (AltGr functionality -- looks like there's already a patch for it on the gerrit review board)?
<ermo[m]>
I'd be happy to help test and push the existing patches over the goal line if you think that might help, though I'll probably need a little bit of hand-holding to get started...
<ermo[m]>
I'm using a 105key Nordic PC keyboard if that matters any.
* ivanholmes
is idle: BRB
<ermo[m]>
The patches look small and contained, but I obviously have no idea how they fit into the wider picture.