When I mean get.
I mean you could use something like
screen = {grabscreen()}
to get the text on the screen in a table.
For one, It means I can finally write my scroll API..
For another. Text effects are even more viable.
And the last one.
Why isnt this in?
There isnt a good reason for it not to be and plenty for it to be.
0
[1.4]Get what is on the screen
Started by libraryaddict, Apr 07 2012 07:45 PM
3 replies to this topic
#2
-
- New Members
- 53 posts
Posted 07 April 2012 - 09:56 PM
Yes, I would love this. The table could be returned in a form like {"TurtleOS 1.3","> cd rom","rom> ls","apis help programs","startup","rom> ","","","","","",""}, spanning as many lines as the screen height. Support 
/>
/>
#3
-
- New Members
- 384 posts
- LocationIn the TARDIS
Posted 08 April 2012 - 12:31 AM
EatenAlive3, on 07 April 2012 - 09:56 PM, said:
Yes, I would love this. The table could be returned in a form like {"TurtleOS 1.3","> cd rom","rom> ls","apis help programs","startup","rom> ","","","","","",""}, spanning as many lines as the screen height. Support />
/>Offtopic: Nice paradoxon! If you don't mind I'll add it to my signature
#4
-
- New Members
- 477 posts
- LocationPoland
Posted 08 April 2012 - 06:20 AM
But this is possible already by wrapping term API and making it store the data.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
