@Callback() references in Macros - changes with PB6.21 ?
Posted: Sat Apr 19, 2025 9:52 am
Hello all,
while PB6.21 is mostly running well I have a problem with some new behaviour introduced with PB6.21...
The following snippet is taken from a large module, which was running fine until PB6.20.
But now causes an error message with the debugger (see the comment in the code), while it's still running without debugger.
Do I need to change all codes written in this way, and how? Or could it be a debugger problem?
Thank you for your help and Happy Eastern! 
while PB6.21 is mostly running well I have a problem with some new behaviour introduced with PB6.21...
The following snippet is taken from a large module, which was running fine until PB6.20.
But now causes an error message with the debugger (see the comment in the code), while it's still running without debugger.
Do I need to change all codes written in this way, and how? Or could it be a debugger problem?
Code: Select all
Macro filter(callback, lParam=0)
to_filtering=lParam
CustomFilterCallback(callback)
EndMacro
Procedure filter_callback_1(x, y, source_color, destination_color)
; do some stuff...
ProcedureReturn source_color
EndProcedure
OpenWindow(0, 0, 0, 300, 200, "Test", #PB_Window_SystemMenu)
StartDrawing(WindowOutput(0))
filter(@filter_callback_1(), invisible_color_) ; <= gives a "CustomFilterCallback(): the procedure given in @Callback() doesn't have the needed argument or return value" error!
StopDrawing()
Repeat
event = WaitWindowEvent()
Until event = #PB_Event_CloseWindow