PureBasic 4.40 Beta 3 released

[graves]

On CallFunctionFast command:

From Help on PB 4.31

Note: this function is not very flexible and can't handle double/quad parameters

From Help on PB 4.40

Note: this function is not very flexible and can't handle string/float/double/quad parameters

Why can not I use strings now?

EDIT:
On Prototype command, PB 4.40 help not show string type (Can it be a mistake?):

Unlike CallFunction(), it can deal with double, float and quad variables without any problem

[blueznl]

Because passing strings no longer works, you have to pass the adress of the string, using @string.s

[Kale]

Maybe because it is not as simple as you think ?

Maybe not, but pretty important don't you think?

[jack]

perhaps somebody with a lot more expertise than me could write an Xcode plug-in for PB

[somic]

Thanks for the update.

I will replace immediately the 4.40B2 and let you know if any problems is found.

Regards,
Somic

Congratulations:
- 16463 lines of anmXNpp plugin code compiled without problems
- Project manager improved in stability and useability

one only strange behaviour I've to investigate further:
when I compile the 16000+ lines of code
* with the instruction: ret = sendmessage_() the compiler claims (and don't crash)
* with the instruction: ret = WaitForInputIdle_() the compiler doesn't claim but crashes

This was also in with PB 4.40 (x86) B2 but not with PB 4.31 that used to claim (and don't crash)

Here you can find the Error Signature:
http://www.semelinanno/downloads/pb/Error_Sign.zip (Form, File dmp & txt)

[klaver]

Are there plans of adding to the docs some fuctions before 2012 (end of the world lol)?

Code: Select all

ServerID()
EventwParam()
EventlParam()

[netmaestro]

EventwParam() and EventlParam() have been around for a long time but have always been unsupported. I doubt they'll ever find their way into the official docs.

[aaaaaaaargh]

Hello,
there seems to be a difference in the way PB4.4beta3 (win/x86) behaves compared to 4.3
The following code (to get font metrics):

Code: Select all

  CreateImage(1,64,64)
  ok = LoadFont(1,"Arial",24)
  dc = StartDrawing(ImageOutput(1))
  DrawingFont(ok)
  GetTextMetrics_(dc, @TxtMetrics.TEXTMETRIC)
  Debug "Font Metrics average="+Str(TxtMetrics\tmAveCharWidth)+" max="+Str(TxtMetrics\tmMaxCharWidth)
  StopDrawing()

Will return the correct values on pb4.3:
Font Metrics average=14 max=85
but in pb4.4beta3 it returns:
Font Metrics average=7 max=14
regardless of the font used. Hmmmm

[netmaestro]

Pretty much the new reality with 4.40 as the device context is configured the way the PB 2DDrawing library needs it. If you run across something like this you'll have to just go a bit further with API:

Code: Select all

CreateImage(1,64,64)
ok = LoadFont(1,"Arial",24)
dc = CreateCompatibleDC_(#Null)
oldimg = SelectObject_(dc, ImageID(1))
oldfont = SelectObject_(dc,ok)          
GetTextMetrics_(dc, @TxtMetrics.TEXTMETRIC)
Debug "Font Metrics average="+Str(TxtMetrics\tmAveCharWidth)+" max="+Str(TxtMetrics\tmMaxCharWidth)
SelectObject_(dc, oldimg)
SelectObject_(dc, oldfont) 
DeleteDC_(dc)

It isn't considered a bug and it's unlikely to be changed: http://www.purebasic.fr/english/viewtop ... =4&t=39246

[aaaaaaaargh]

Pretty much the new reality with 4.40 as the device context is configured the way the PB 2DDrawing library needs it. If you run across something like this you'll have to just go a bit further with API:

Code: Select all

CreateImage(1,64,64)
ok = LoadFont(1,"Arial",24)
dc = CreateCompatibleDC_(#Null)
oldimg = SelectObject_(dc, ImageID(1))
oldfont = SelectObject_(dc,ok)          
GetTextMetrics_(dc, @TxtMetrics.TEXTMETRIC)
Debug "Font Metrics average="+Str(TxtMetrics\tmAveCharWidth)+" max="+Str(TxtMetrics\tmMaxCharWidth)
SelectObject_(dc, oldimg)
SelectObject_(dc, oldfont) 
DeleteDC_(dc)

It isn't considered a bug and it's unlikely to be changed: http://www.purebasic.fr/english/viewtop ... =4&t=39246

I understand that...........now
thanks!