PureBasic Forums - English

Ok, changed. But that file is not a lib, only a test program which anybody can modify if there's conflict. But you're right about library command names, they should be choosen carefully. I'll write something about that in the help file.

maybe fred will put some sort of conflict cheaker

I think the majority of conflicts would be quickly resolved on these boards, as soon as somebody released a library.

But if needed, one way could be to use the library file name as the prefix for functions, as there cannot be two files of same name in the same folder.

The prefix idea, whatever is used (author, file, complete sentences etc) is also a clue that there is a library dependency when code snippets are released.

after installing Tailbite, (and after rebooting) there's no tailbite
in tools menu, how do i set it up manually using Tools/Config Tools...?
Pb is installed in: C:\Program Files\PureBasic
and i have: C:\Program Files\PureBasic\TailBite

[edit] re-installed Tailbite several times, still no Tailbite in Tools Menu [/edit]

using WindowsXP

Weird, I'll have to check that. Select C:\Program Files\PureBasic\TailBite\TailBite.exe as command line, "%FILE" as argument and TailBite as menu item name. Once you made that, you can set several command line options from TBManager.

thank you sir.

jack, could you send me your Tools.prefs file without TailBite added (in the PureBasic dir) to help me find the problem?

my Tools.prefs. just had a strange thing happen on boot up, had a requester pop up:

the file "C:\Program" may conflict with some programs,
rename to "C:Program1" ?

don't know if this related to my menu problem, but just in case.
thanks El Choni for your hard work.

Thank you very much, you found a new bug. I think it's fixed, can you check it?

yes, that fixed it. thanks

RValois wrote:Hi El_Choni,
Thanks for the fix, the recursive procedure is now generated correctly....

Yes for normal procedures, But not for ProcedureDLL's .

Fixed, thanks, Rings

I think there is a bug when calling COM objects, seems like the method params don't accept expressions like casting into structures or variables accesed through a pointer, in the render method of the IPicture:

ppic\render(*myst\var,.........) ;PB crashes

var = *myst\var
ppic\render(var,.........) ;works

-----------------------------------

ppic\render(........., @rc.RECT) ;PB crashes

rc.RECT
ppic\render(.........., @rc) ;works

it's strange because TB compiles the lib without erros but PB crashes when running the code. it's in a large lib, i'll try to make a small test, i don't think is specific to the IPicture object.

Hi El_Choni,

i don't know if this prob has already been reported.

Code :
If you create the lib, you will have a FASM error. A jmp to an undefined symbol.
After taking a look to the asm code, the problem comes with the End pb instruction.

The label to go to the end of tha app is Ok in the shared asm file, and in my try :

Public Examples_withe_End__PB_EOP_NoValue

But inside the asm file for the function, there is no extrn Examples_withe_End__PB_EOP_NoValue declaration

But i think that the label must only be _PB_EOP_NoValue because the real end of code will be in the main PureBasic code.

Have a nice week-end and many tks for TB

Mine was a PB bug, not from TB, i'll post it in the bug forum..