Welcome Guest. Please Login or Register. Apr 1st, 2018, 03:52am
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. We apologize Conforums does not have any export functions to migrate data. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
Thank you Conforums members.
Speed up Liberty BASIC programs by up to ten times!
Compile Liberty BASIC programs to compact, standalone executables!
Overcome many of Liberty BASIC's bugs and limitations!
I recently discovered that in LBB, popupmenu allows branches to subroutines, while popupmenu in LB4x does not. Is this a planned feature?
In LBB a common routine is used for processing 'handlers'. It is used by buttons/checkboxes, combo/listboxes, menus/popupmenus, timer, trapclose, resizehandler, spritetravelxy and when events.
As a result, in every case you can specify either a label or a sub. So whilst allowing a popupmenu handler to be a sub was not exactly "planned" it naturally follows from the use of shared code.
I don't think I realised that LB 4 doesn't allow sub handlers for popupmenus. Since ordinary 'drop down' menus do, it seems an anomaly.
Logged
