Hi Frank,
Yes. You are compiling DLL, so to make changes visible you must create new machine code soup after each changeit's necessary to compile the tomdk every time new, when I am making changes ???
As you are compiling with Oxygen magic, you could, in theory, let part of the file source external, so Oxy would compile it from string at the time of calling module ( thats wild, but possible ).
ThinBasic modules work on simple and ellegant principle. They are like normal DLLs + the following:How can I know what's possible with this "T" file
- In compiler of your choice (this time Oxygen) you create custom functions
- In those custom functions, you use ThinBasic SDK functions to take control over parsing parameters
- You "register" the custom functions by "thinBasic_LoadSymbol" in LoadLocalSymbols
Of course, it does not have to be named T, just change fdll string in your TOMDK to something else, like "thinBasic_LionHeartMegaModule.DLL". So the module can do really anything you manage to compile
Try to browse samples from SDK directory in TB installation to get the general idea.
Petr
Bookmarks