Yes, most tailbited userlibs a incompatible. for example the new optional Parameter FindString breaks many libs.jassing wrote:Can we expect userlibs to be incompatible?
I've always found it slightly odd that the production of a user library isn't a selectable output choice in the compiler options, native to Purebasic and maintained by the team. It's certainly popular enough to warrant such, imho. Maybe someday..Userlibs usually break with every update. I wish it weren't so.
You're right, these (tiny) issues are the reason, why I try to ignore all user libs, if possible.MachineCode wrote:Userlibs usually break with every update. I wish it weren't so.
what about purebasic functions? A lot of examples on the forums do not compile because functions changed/removedts-soft wrote:Yes, most tailbited userlibs a incompatible. for example the new optional Parameter FindString breaks many libs.jassing wrote:Can we expect userlibs to be incompatible?
I'm learning this -- it's unfortunate that people release userlibs and then abandon them it's one reason I won't even pay for userlibs -- I'll pay for source, but not userlibs...Michael Vogel wrote:these (tiny) issues are the reason, why I try to ignore all user libs, if possible.
Other languages seem to handle upgrades a bit more gracefully allowing addons still to work.. I guess the key wiht purebasic is to ignore userlibs and use lib or obj files and link them in...Michael Vogel wrote:I understand, that a small developer team can't maintain tons of libraries and user defined functions -- but I still hope, that commonly used/needed functions will be implemented into standard libraries somewhen in the future. This may be possible for easy integer functions (like Minimum, Maximum) or even for OS/HW depended things (set user level, get CPU load etc.)
+1 for that...MachineCode wrote:It wasn't explained how to do it, however. Maybe someone here could write a converter?
to what?MachineCode wrote:(Also, maybe a mod could edit this topic's subject?).
Progressricardo wrote:Takes sometime to get used to new changes... until new version ads more and more and more changes... Really don't understand the point.
Progress does not mean spoiling old 'Things', it should enhance or at least allow you to use it the old way of doing things - OR -have the option to use the new one in future projects without breaking old ones.skywalk wrote:Progressricardo wrote:Takes sometime to get used to new changes... until new version ads more and more and more changes... Really don't understand the point.
Code: Select all
Debug "#PB_EventType_LeftClick = " + Str(#PB_EventType_LeftClick)
Debug "#PB_EventType_RightClick = " + Str(#PB_EventType_RightClick)
Debug "#PB_EventType_LeftDoubleClick = " + Str(#PB_EventType_LeftDoubleClick)
Debug "#PB_EventType_RightDoubleClick = " + Str(#PB_EventType_RightDoubleClick)
Debug "#PB_EventType_Focus = " + Str(#PB_EventType_Focus)
Debug "#PB_EventType_LostFocus = " + Str(#PB_EventType_LostFocus)
Debug "#PB_EventType_Change = " + Str(#PB_EventType_Change)
If OpenWindow(0, 0, 0, 270, 180, "ComboBoxGadget", #PB_Window_SystemMenu | #PB_Window_ScreenCentered)
ComboBoxGadget(0, 10, 10, 250, 21, #PB_ComboBox_Editable)
AddGadgetItem(0, -1, "Type some text here...")
SetGadgetState(0, 0)
Repeat
Event = WaitWindowEvent()
If Event = #PB_Event_Gadget
Select EventGadget()
Case 0 ; PB_ComboBox_Editable
Debug EventType()
; PB 4.5 EventType() = 5
; PB 4.6 EventType() = #PB_EventType_Change
EndSelect
EndIf
Until Event = #PB_Event_CloseWindow
EndIf