PureBasic 5.00 beta 6 is online !

[Fred]

Hi there,

We are now close to the final release, it's only a bug fix beta. If you can, try to test your regular application with this version, as we believe it is stable enough. It will help us to have a robust 5.00 release, thanks ! You can grab the new beta on your online account as usual.

Enjoy !

The Fantaisie Software Team

[Falko]

Thank you, Fred.

Non Flicker, it's very good

[Droopy]

thanks too

[deeproot]

Thanks from me too! Great work!

Installed - main project compiled and run - no problems thus far, will code and test more over the next couple of days.

[J. Baker]

Cool but any chance the ReleaseMouse() function could be fixed on OSX for the final version?

[Primoz128]

If i could buy PB this year... stupid visa...

[skywalk]

I also had some problems with the Paysite method. Fred told me to use my Paypal account. If you don't have one, then use Paypal 'guest' account. Paypal has lower fees than the other method.

[leonhardt]

and this bug still exists:

Code: Select all

Procedure fa()
 Protected  a.l=23333
 Protected b.f=0.345
Debug a*b
EndProcedure
fa()

Procedure fb()
Protected a.q=23333
Protected b.f=0.345
Debug a*b
EndProcedure
fb()

[Demivec]

@leonhardt: 1. post bugs in the bug forum. 2. Don't repost bugs just because they haven't been solved yet. 3. It is not a bug, you are misusing the 'Debug' statement, you should use 'Debug Strf(a*b)'.

[Primoz128]

I AM using the paypal, and i get some shit about the card... dad said maybe casue he payed 50 € for a program almost a month ago, maybe theres some kind of weird limit...

[Azul]

thanks

[leonhardt]

@leonhardt: 1. post bugs in the bug forum. 2. Don't repost bugs just because they haven't been solved yet. 3. It is not a bug, you are misusing the 'Debug' statement, you should use 'Debug Strf(a*b)'.

"you should use 'Debug Strf(a*b)'."
No,I don't think so,please explain this to me,test it yourself:

Code: Select all

Procedure.l fa()
 Protected  a.l=23333
 Protected b.f=0.345
ProcedureReturn a*b
EndProcedure

Debug StrF(fa())

Procedure.l fb()
Protected a.q=23333
Protected b.f=0.345
ProcedureReturn a*b
EndProcedure

Debug StrF(fb())

win7 32bit

[MachineCode]

please explain this to me

Your procedures are not of Float type, yet they're calculating floats (the "b.f" variable). So, look at this:

Code: Select all

Procedure.f fa()
  Protected a.l=23333
  Protected b.f=0.345
  ProcedureReturn a*b
EndProcedure

Debug StrF(fa())

Procedure.f fb()
  Protected a.q=23333
  Protected b.f=0.345
  ProcedureReturn a*b
EndProcedure

Debug StrF(fb())

Debug output:

Code: Select all

8049.8847656250
8049.8847656250

No bug.

[leonhardt]

please explain this to me

Your procedures are not of Float type, yet they're calculating floats (the "b.f" variable). So, look at this:

Code: Select all

Procedure.f fa()
  Protected a.l=23333
  Protected b.f=0.345
  ProcedureReturn a*b
EndProcedure

Debug StrF(fa())

Procedure.f fb()
  Protected a.q=23333
  Protected b.f=0.345
  ProcedureReturn a*b
EndProcedure

Debug StrF(fb())

Debug output:

Code: Select all

8049.8847656250
8049.8847656250

No bug.

yeah,that's because your procedures return float types ,it's ok,but when they return integer,the first procedure return 8050 while the second return ZERO,if one returns zero then the other should do the same, doesn't it ? but MY code's output is obviously different, then can you explain this defference? please just point out where is the error of MY code.the only difference is between" a.q" and "a.l",aren't they both integer types?

[MachineCode]

I read in the manual (or here on the forums?) that once you do a calc with a float, the result is converted to a float automatically; hence why you need to make the procedure return a float value ("Procedure.f").