Quote:Also if anyone can show me how to store the menu strings inside the UDT! Then youll get a +1 from me!
Simple, for me, is using long strings. I used them in my very simple GUI for any array I needed, that PLUS the split routine Yes not exactly most effecient but it works, perfect for Text Property of List Boxes. Long strings are easy to append (no dim _preserve) and easy slice and dice and substitute whole sections of strings. I use them in my Fval() (like Eval of other BASICs) code too which is core to my Interpreter work. UDT will take a variable length string since way back around time of QB64 v 2.0, you may have missed the change, by Luke, I think it was. Alas! they don't store well to file like a fixed string would.
BTW let me plug my drop down menus lecture (because no one else will
) that starts here with exploring menus:https://qb64phoenix.com/forum/showthread...8#pid17118
724 855 599 923 575 468 400 206 147 564 878 823 652 556 bxor cross forever