A complete code browser for PureBasic [Windows]
Re: A complete code browser for PureBasic [Windows]
Hi Zapman, if you try to compile the sources with PB6.20 or later, you'll get an error. It works fine with 6.12. Check this thread:https://www.purebasic.fr/english/viewto ... 76#p637976

Re: A complete code browser for PureBasic [Windows]
Hello le_magn,le_magn wrote: Sun Mar 23, 2025 1:10 pm Hi Zapman, if you try to compile the sources with PB6.20 or later, you'll get an error. It works fine with 6.12
Thank you very much for your feedback. I can't reproduce the problem on my system, neither with PB6.2 x64 nor PB6.2 x86.
Could you point me to the line where the error occurs?
Re: A complete code browser for PureBasic [Windows]
Thank you very much. I'll fix that tomorrow.
Last edited by Zapman on Mon Mar 24, 2025 11:04 am, edited 1 time in total.
Re: A complete code browser for PureBasic [Windows]
Hello le_magn,
After examining the files, I see that there are no problems with the current version of "TOM_Functions.pbi".
The version shown in your screenshot is not the current version. It seems that you didn't perform a full program update, or you didn't open the correct folder when compiling.
Re: A complete code browser for PureBasic [Windows]
Hi, i try again, deleting all pbbrowser source, download it again and same error on compiling, i try also with a clean Purebasic installation and same result, TOM_Functions is version 1.3
p.s. this is not a real problem, i can modify the code by removing ".i" or compile it with 6.12
UPDATE: I cheched TOM in your website and i found a version 2, but in the pbbrowser are included the 1.3
If I replace TOM 1.3 with TOM 2 I get several errors for duplicate procedure names etc. due to the FontDescription file
p.s. this is not a real problem, i can modify the code by removing ".i" or compile it with 6.12
UPDATE: I cheched TOM in your website and i found a version 2, but in the pbbrowser are included the 1.3
If I replace TOM 1.3 with TOM 2 I get several errors for duplicate procedure names etc. due to the FontDescription file
