Mistrel wrote:What I meant so say what that if I declare a procedure inside of a Tailbite library as Procedure and not ProcedureDLL the command will appear as a hint at the bottom of the IDE when the library is included by the compiler. PB will error on compile because this procedure isn't really available.
i just tested this with PurePDF and an internal procedure ipf_LocalDecimal(), but haven´t found anything unusual Do you have something more to test it (Library / source-code ...)
IceSoft wrote:Tailbite creates subsystem userlibs not in the correct subsystem subfolder.
e.g:
SubSystems\DirectX9\PureLibraries
Correct is:
SubSystems\DirectX9\PureLibraries\UserLibraries
It's historical, because SubSystems\xxxxx\PureLibraries\UserLibraries was broken in PB4.00 / PB4.01.
Anyway SubSystems\xxxxx\PureLibraries\ works also for userlibraries, and most userlibraries use this scheme.
Imho, it's not correct or incorrect to put userlibraries in PureLibraries, it's only tradition. And in Subsystems, you can't confuse them with genuine PB libraries like in %PB%\PureLibraries, because of the subsytem name.
For free libraries and tools, visit my web site (also home of jaPBe V3 and PureFORM).
IceSoft wrote:Tailbite creates subsystem userlibs not in the correct subsystem subfolder.
e.g:
SubSystems\DirectX9\PureLibraries
Correct is:
SubSystems\DirectX9\PureLibraries\UserLibraries
It's historical, because SubSystems\xxxxx\PureLibraries\UserLibraries was broken in PB4.00 / PB4.01.
Anyway SubSystems\xxxxx\PureLibraries\ works also for userlibraries, and most userlibraries use this scheme.
Imho, it's not correct or incorrect to put userlibraries in PureLibraries, it's only tradition. And in Subsystems, you can't confuse them with genuine PB libraries like in %PB%\PureLibraries, because of the subsytem name.
Sorry that is the directory structure created with the latest 4.20 (Beta1).
SO it is not tradition.. it is an advise from Fantaisie Software. Right?
IceSoft wrote:Sorry that is the directory structure created with the latest 4.20 (Beta1).
SO it is not tradition.. it is an advise from Fantaisie Software. Right?
An advise if you want.
I explained the reason : the 'UserLibraries' directory is disabled in 'SubSystems' in PB4.00/PB4.01.
And all I am saying is there is no functional reason ; your app won't work any better if you choose one or another directory. It just separates genuine libs from user libs.
For free libraries and tools, visit my web site (also home of jaPBe V3 and PureFORM).
IceSoft wrote:Sorry that is the directory structure created with the latest 4.20 (Beta1).
SO it is not tradition.. it is an advise from Fantaisie Software. Right?
An advise if you want.
I explained the reason : the 'UserLibraries' directory is disabled in 'SubSystems' in PB4.00/PB4.01.
And all I am saying is there is no functional reason ; your app won't work any better if you choose one or another directory. It just separates genuine libs from user libs.
Not my prog...Thats right.
But Tailbite is working wrong:
'Prompt confirm on deletion of previos library with same name.'
The reason of course is the copy of the userlibs into the deepher dir structure by me.
But it is helpfull to use always the same.
If Tailbite and PB have no prob with the dir structure...so why PB has the 'Userlibraries' folder on each subsystem generated?
[26] JAN 2th 2008 TailBite v1.3 PR 1.864
- TBManager : correction of Subsystem folders (found by IceSoft)
- TBManager : added creation of Subsystem folders
see first post for more deatils.
I got a unclear Messagebox if I have checked the 'Prompt confirm on deletion of previos library with same name.'
look here:
If I press Ja(Yes) the existing lib will be removed
If I press Nein (No) I got a text 'Error' Line: -1 Exit program?
(Line: -1 should be also have a understanding text)
Last edited by IceSoft on Thu Jan 03, 2008 10:32 pm, edited 1 time in total.
[27] JAN 3th 2008 TailBite v1.3 PR 1.865
- fixed stack issue when 'Prompt confirm on deletion...' was checked (found by IceSoft)
- fixed mispelling of 'user library already exist.'
I thought I could speed up the time it took to compile one of my larger libraries by encapsulating sections in CompilerIfs. I found that by doing this the functions no longer worked but library itself did not decrease in size as expected. Compile time also was not noticeably faster and function hints still display at the bottom of the IDE for functions that should have been ignored by the compiler.
;#Lib_GroupName=0 ; This line is commented out
CompilerIf Defined(Lib_GroupName,#PB_Constant)
ProcedureDLL ProcName()
; This function is still recognized by Tailbite?
EndProcedure
CompilerEndIf