*** deleted ***
*** deleted ***
Last edited by John Spikowski; 18-09-2013 at 01:42.
sounds familiar...
Just some nosy questions:
What about that IUP? It's some .dll that I can find in your scriptbasic-examples-thread I guess?
And- why are the statements as in IupSetAttributes(btn1, "TITLE=Button1, EXPAND=HORIZONTAL") in quotes as it were strings?
I think that's not a good idea if you think about adding code-spell-correction one day.
And - are those string-statements maybe case-sensitive?
Edit-
What makes me wonder too:
Function_GetPtr
help says: "Returns the internal pointer of a script function or sub"
Returned pointer is thinBasic internal pointer. It has no meaning outside thinBasic.
Do not confuse it with machine or code pointers.
Last edited by ReneMiner; 01-03-2013 at 20:05.
I think there are missing some Forum-sections as beta-testing and support
just edited my last post- so please have another look at it
I think there are missing some Forum-sections as beta-testing and support
Just snooped around in the helpfile because I thought it might be that thinBasic is not able to pass pointers to external functions. This is what I found about
but it's just a guess since I have no idea about the internal stuff."External function declarations"
There are still some limitations regarding type of parameters thinBasic is able to pass to external functions.
If you are in trouble, please visit thinBasic forum and leave a message regarding the problem you are facing and possibly specify an exact example. We will do our best to try to solve the problem as soon as possible.
Maybe you could store the result of Function_GetPtr in another variable and pass this?
Last edited by ReneMiner; 01-03-2013 at 20:22.
I think there are missing some Forum-sections as beta-testing and support
Hi all,
as I said many times in this forum, unfortunately there is no way (at the moment) to pass thinBasic script function pointer simply because there is no function and there is no pointer.
When an external function ask for a function pointer or a code pointer they are referring to pointers to machine code currently running in the current process.
But thinbasic functions are not translated into machine code, they are just text (simple and damn text) parsed and interpreted on the fly by thinBasic engine.
thinBasic source code is never translated/converted/compiled into machine code of pcode or intermediate code (or whatever you call it)
thinBasic source code is just text during all the process of thinBasic source code execution.
In any case, it is some time (some months) I'm thinking about this trying to find a solution.
What I have in mind is to create a sort of "machine code alias" for each thinBasic source code function present into a script in such a way every source code function (or sub) has a machine code ghost function into thinBasic engine in such a way to pass pointer of the machine code ghost function to external libraries asking for a callback.
Sooner or later ...
www.thinbasic.com | www.thinbasic.com/community/ | help.thinbasic.com
Windows 10 Pro for Workstations 64bit - 32 GB - Intel(R) Xeon(R) W-10855M CPU @ 2.80GHz - NVIDIA Quadro RTX 3000
Well,
thanks to you too for spending your time in showing how to use IUP library in thinBasic.
I really appreciate it
Ciao
Eros
www.thinbasic.com | www.thinbasic.com/community/ | help.thinbasic.com
Windows 10 Pro for Workstations 64bit - 32 GB - Intel(R) Xeon(R) W-10855M CPU @ 2.80GHz - NVIDIA Quadro RTX 3000
"Byval ih as Long" ??? Why?
I think there are missing some Forum-sections as beta-testing and support
Bookmarks