0 Members and 4 Guests are viewing this topic.
In other news, Frey continues kicking unprecedented levels of ass.
White rectangles and (why hasn't this been implemented yet) white lines. Also, inverted lines.
Quote from: Freyaday on November 11, 2011, 11:51:25 pmWhite rectangles and (why hasn't this been implemented yet) white lines. Also, inverted lines.Use drawinv ... drawinv for that
Also, have you considered my past idea? It was being able to absorb appvars into executables, the way you can with TI-OS pictures by going like this: [Pic1]->Pic1 . It would be awesome to be able to go like this: [appvBLAH]->GDB1
the thing with using lots of DrawInv statements is that it's slow. I agree with Freyaday.Also, have you considered my past idea? It was being able to absorb appvars into executables, the way you can with TI-OS pictures by going like this: [Pic1]->Pic1 . It would be awesome to be able to go like this: [appvBLAH]->GDB1
Quote from: buttsfredkin on November 12, 2011, 04:30:13 pmthe thing with using lots of DrawInv statements is that it's slow. I agree with Freyaday.Also, have you considered my past idea? It was being able to absorb appvars into executables, the way you can with TI-OS pictures by going like this: [Pic1]->Pic1 . It would be awesome to be able to go like this: [appvBLAH]->GDB1what, exactly, would be the point of that? appvars are supposed to be variables, which can be modified during runtime and used to store data, but that takes effect only during compilation.