VANYA wrote: ↑Feb 19, 2022 16:00
SARG wrote:Yes for my last sentence I was thinking also about UboundIncBin
Of course, I did not just write in the help that the IncludeBinary and Catch_image functions are connected.
Mysoft wrote:because thats the only way to have an image buffer from pointer, since there isnt a function to get/set bitmap bits
No, not the only one. Do you not know how to get pixels in GDI? Or do you not know how to get pixels in GDI+?
I understand if you don't know how to get pixels in linux gtk , but even here it's enough just to look at the source code of the library under linux 2D_DRAW function Fillrectdraw and you will understand how to get a pointer to pixels. It is irrational to create a function in the library for every sneeze, something must be written by the users themselves.
Mysoft wrote:and yes i'm using in a hacky way
Well... I have neither time nor desire for your experiments. For experiments, please create a separate topic in section "Libraries Questions" and there you can write as much as you want about the fact that your examples crash or something does not work. In this thread, I want to receive a bugs report from users on normal use of the library. And I don't want every time you write about a problem to try to guess what you've done there again. Please don't be offended.
oh come on, they are not just experiments, i'm doing REAL tests on the library, and while i push further sometimes on what is documented and what not, all that i reported actually worked on windows, and there was no documentation that they were not avaliable, so i use common sense for those, like having the catch that can ONLY work with that specific incbinary, is counterintuitive, maybe it used better words on the russian help hehe, and while i understand that i could pad with native functionality on either side, but i'm testing how much the library can do as crossplatform, because thats the only reason for that library to be actually useful hehe , and a top grade library, with little bloat.
because of this library i'm also learning how weak GTK is compared to WINAPI, and so on, so i'm pushing it to the limits, i may create a whole section of documentation, just exposing all differences that i could find, that ACTUALLY exist between the API... for example, on the SetTimer callback function, the sample prototype have it as "function" but it does not explain what the return value of that means... on linux you need to return TRUE for the timer to continue ticking, on windows, it does not matter, and the fact that on linux window and gadgets are different, but on windows they are the same thing, (so other than adding such warnings on documentation, i think a section for differences is crucial, because theres the dillema between allow the functionality, and negate the functionality (when using w9 functions at least).
and really thats how i test stuff, i can open another topic, but as you see its one of the few libraries that i see potential, so i want to help, and improve make this the best it can without being too bloaty, so you want to discuss those details in another place, because i'm learning from the library and just its documentations and possibilities, because this "works on windows, but on linux" is kinda a responsability of the library to pad eventually
so yeah most of the problems so far, is because things were hidden from me where they shouldnt be, or they didnt worked the same way on linux/gtk/64bit, so theres a lot for me to just "guess/learn/test", but that people would encounter sooner or later hehe, specially with the difference between integer and long on 64bit (because some handles were used as integers when they should be pointers hehe), that i'm double checking everytime with the documentation to avoid those... so imo everything that returns a pointer, but requires 64bit integer on 64bit, should be returned as handles like the hwnd... which have the benefit of the compiler catching those, when they are not "byref" parameters
if you use discord and want to talk there, thats fine by me, the forum isnt the most appropriate place, but just dont be too agressive on people that value your project (like you scared away that other guy that wanted to use it in C)
also on linux i want to try to get the gtk3 version working, that i couldnt so far due conflicts with gtk2, because ubuntu comes with gtk3 installed but not gtk2
and so i'm using all my free time, to advance one step ahead, next will be compile the source of this, before i can start peeking on its source, because that will require me to ignore the OOP parts, and see how much unified the code is for linux\windows (with only stuff that differs on system specific folders), but seeing how the .bi files greatly differ on windows\linux, i think it would be better to unify those more, so i will keep learning to be able to help with the linux part that i dont have experience hehe