This is a short list of things which were already mentioned, but seem to be forgotten:
1. DC_XbpBrowse:ForceStable(): This method still replaces the errorblock during the force-stable-process, so there is no access to the error system if there are errors inside color codeblocks of the browse, for example.
2. If the DCMESSAGEBOX is used with the MOTION clause, every move with the mouse over parts with messages forces the complete getlist to be evaluated (getwhen). This slows down the repaint of items in huge getlists. You promised to replace this with the LEAVE/ENTER-slots (some months ago). The MOTION clause is useless until then.
3. Clauses like WHEN, TOOLTIP and maybe others would still be helpful for buttons added with DCREAD ADDBUTTONS CUSTOM to the getlist. (Would it be hard work to create an option BUTTONSTOP for those buttons, so they appear on top of the dialog?)
4. If DC_BrowseColor() is used to show toggled background colors, a browse with an odd number of rows changes the background colors with every RefreshAll(). This happens with arrays and tables.
They were some other (cosmetic) things The Wizard From Idaho promised to integrate, but since I can't access the legacy board anymore, please assume them to be not urgent/important/really necessary.

Tom.