Hi Barney,
Cool deal then. With EBasic you can either use the .inc or the .incc for the import delcarations not both. If you want the highlighted commands just setup an .incc to import the functions with the $command and stick in the bin directory.
But, Paul told me that .incc command paks are not officially supported with EBasic and he plans to drop the .incc stuff all together in EBasic 2.0. So if you have just the .inc include file that will probably be best for now.
I just now asked him if he plans for some kind of keyword highlighting for command names themselfs that we could add in the future. hopefully he will.
Just so I wont reivent wheels here ;) , what kind of examples if any you've included with your EBasic support? I have the setup.bb converted over as I was wanting to port over the Mak samples. Also was wanting to make examples for the bbSetBlitz3DDebugCallback and bbSetBlitz3DEventCallback functions. Actually, I'll do them anyway just for the fun of it just in case i dont get a reply for awhile.
Also, did you just generate the b3d.lib file from the 'create import library' and worked off of that? I had renamed the the b3d.lib to blitz3dsdk.lib to try to keep it on par with the blitz3d sdk distribution, but it does feel like it's a step that isn't needed.
thx
Cool deal then. With EBasic you can either use the .inc or the .incc for the import delcarations not both. If you want the highlighted commands just setup an .incc to import the functions with the $command and stick in the bin directory.
But, Paul told me that .incc command paks are not officially supported with EBasic and he plans to drop the .incc stuff all together in EBasic 2.0. So if you have just the .inc include file that will probably be best for now.
I just now asked him if he plans for some kind of keyword highlighting for command names themselfs that we could add in the future. hopefully he will.
Just so I wont reivent wheels here ;) , what kind of examples if any you've included with your EBasic support? I have the setup.bb converted over as I was wanting to port over the Mak samples. Also was wanting to make examples for the bbSetBlitz3DDebugCallback and bbSetBlitz3DEventCallback functions. Actually, I'll do them anyway just for the fun of it just in case i dont get a reply for awhile.
Also, did you just generate the b3d.lib file from the 'create import library' and worked off of that? I had renamed the the b3d.lib to blitz3dsdk.lib to try to keep it on par with the blitz3d sdk distribution, but it does feel like it's a step that isn't needed.
thx