I think to have discovered some weird and really annoing things regarding fx functions...
First and minor:
WaterRippleBrush() function accept zero as Wave lenght parameter but that locks the entire system and you have to reset...
The below issue happens only on AmigaOS4.1Upd4 since I tryed it also on MOS 2.7 and dont happens(i.e. it works as expected)...
But was weird the same imho...
Major issues:
All the fuinctions that locks the system here on AmigaOS4.x have a really strange behaviour...
Try the code below:
Code: Select all
@DISPLAY 1, {Width = 800, Height = 600}
LoadBrush(1, "ram:test.png")
TextOut(#CENTER, #CENTER, "Please Wait, processing image...")
EmbossBrush(1, 8)
DisplayBrush(1, #CENTER, #CENTER)
WaitLeftMouse()
The TextOut() function will display him text only a moment after the EmbossBrush() function have finished the elaboration and than the image was displayed...
If you comment the DisplayBrush() line than you get the TextOut() message displayed after elaboration finished but only after...really weird no? Since Hollywood wasnt multithreaded that dont have any sense right?
In theory before starts EmbossBrush() function Hollywood have to process the TextOut() function and complete its task than (and onoly than) continuing processing images...no?
Also if AmigaOS4.x have the bug you tell us regarding the locking of the system while using such functions why The TextOut() wasnt processed before EmbossBrsh() by Hollywood interpreter? Wasnt odd?
Thank you!