? "SmallBASIC " + (right("0.12.19", 5))i.e. just drop the "0.", that will keep continuity with the older versions.
@chiswsMan, If you can get 64 bit working through the Tabbed Editor... (Here I just vent, if you don't need that don't worry about it, but it is feedback from one user / fan)Very frustrating for me personally is the complete closing of SmallBASIC when I hit the top right X box.I am in habit of writing a line testing editing or writing the next. In QB64, I have to close the Run \ "Output window" before (well not actually, it's just that I don't need 10 different versions running at same time...) before going back to editor. I know the way back for SB is just a right mouse click and then another (with built in editor), it's just not habit. It is handy to have output window there while making edits. What makes it super frustrating is when I accidentally X out of a run the code hasn't been saved, sometimes I might get a warning about save but I have lost so much that I have to go back and write again ugggh. Do that twice in a row and well... it's not fun! Sure it's my problem, it's also my choice which Basic I pick to work and thank goodness there are still good choices one can make, none are perfect. When I first started SB you had tabbed file editor and I dropped my search for better Basic but I wonder if I encountered SB later with the built-in editor? Would I even be here now? probably not.
Are you talking about the fltk version or the sdl version?
I also have to use GDI+ functions to create a graphics screen, and that's a bit of a nightmare too,
QuoteI also have to use GDI+ functions to create a graphics screen, and that's a bit of a nightmare too,are you sure is GDI+ or just GDI because GDI is freakin simple also GDI+ is juat little bit more resource hungry and is simple too.i use both in Oxygen
line x, y, x1, y1, rgb(255,255,0)at x2, y2:? "Hello"
pToken := Gdip_StartUp()
pBitmap := Gdip_CreateBitmap(W, H)
G := Gdip_GraphicsFromImage(pBitmap)
pen := Gdip_CreatePen("0xFFFFFF00", 1)
Gdip_DrawLine(G, pen, x, y, x1, y1)
Options = x%x% y%y% cFFffFFff r4 s20 Underline Italic
Gdip_TextToGraphics(G, "Hello", Options, "Arial")
Quote from: Aurel on February 15, 2021, 11:38:46 AMQuoteI also have to use GDI+ functions to create a graphics screen, and that's a bit of a nightmare too,are you sure is GDI+ or just GDI because GDI is freakin simple also GDI+ is juat little bit more resource hungry and is simple too.i use both in OxygenGDIplusWell, of course, something simple for you might be difficult for me. I haven't done a lot with it, because the examples I found were a bit baffling, but I recently got some help and it's become a little less obscure. However, what I obviously meant is in comparison to SmallBASIC, which gives you a graphics output screen without doing anything, AutoHotkey requires you to define one, which takes a number of steps. Let's compare, something like drawing a yellow line and printing some white text on the graphics screen:In SmallBASIC, it might be something like:Code: [Select]line x, y, x1, y1, rgb(255,255,0)at x2, y2:? "Hello"That's it (apart from defining x, x1, y and y1. Run it and it's there, done. (Also, if you want the logical colours, you can just use 14 instead of the rgb.)In AHK, first we have to start GDI+Code: [Select]pToken := Gdip_StartUp()...assuming it's on our system, or we have to check first if we don't know. Then, we create a bitmap and get its pointer:Code: [Select]pBitmap := Gdip_CreateBitmap(W, H)Then, we get a pointer to the graphics thingumajig :Code: [Select]G := Gdip_GraphicsFromImage(pBitmap)....