10-16-2023, 02:52 PM
(10-16-2023, 12:51 PM)bplus Wrote:(10-16-2023, 01:00 AM)James D Jarvis Wrote: _PRINTSTRING (x,y,imagehandle),string
May I ask: If we can have output directing to image handles... why not another window? Don't really need a complex event model in QB64 for that do we?
Screen _newimage(W,H,mode),windowhandle would be awesome, with windowhandle being managed for the QB64 programmer as any other image handle so pset(x,y),color,imagehandle could use the windowhandle similar to the imagehandle if making such modifications.
Might mess up the Screen default assumptions in old code, ie having to specify a screen handle to Screen command??? I don't know, just guessing at possible obstacles.
Overloaded subs/functions are already in use for the compiler aren't they? It's fairly common in C/C++. The default can just remain there. That's how the image handles would be added to other output commands, wouldn't it?