Multi-application tunneling
-
Basically, would it be possible if we could have a element called , say PRTT which is like portal in, but it
PASSES PARTICLES TO ANOTHER WINDOW
Then we could have OP microprocessing and esssentially upsize our screens!!!
Consider shared memory regions etc?
I know it is a big ask... but yeah. :D
-
@asdf123 (View Post)
From what I could understand, you are essentially suggesting a larger TPT window, which has been rejected multiple times before.
And if this particle is implemented, what will happen to the particles which appear in another window? Will they keep running without the user seeing whatever is happening? -
what i got from this is a portal that transfers stuff from one powder toy window to another, is this right? If so i'ld imagine you'lld have to do some thing with file system from a lua perspective ,IDK not an expert at this stuff... I wouldn't trust my self to test i've writen horrible scripts the I wish never to see again(ones that spammed me with windows or shutdown my computer and all the computers around it) code can be evil :P
Edited once by jward212. Last: 5th Nov 2014 -
@asdf123 (View Post)
How do you figure people will upload saves with this element? Just have a save launch 500 powder toy windows on some poor sod's computer, just to run a processor? -
This would definitely be complicated to implement. I think a better (but even more complicated) idea would be to have multiple Simulation*s running at once, and then we could figure out how to pass things between layers later. Simulations in tpt++ are sort of close to being able to work like this but I think there are just a few problems.
-
Edited once by CeeJayBee. Last: 5th Nov 2014
-
@CeeJayBee (View Post)
It just saves them as stamps when you aren't using them. They aren't all simulating at once. Also over half is still the old c code just with a .cpp extension. -
-
could probably have some sort of networking that absorbs particles like prti on one side,creates a buffer to send to the other side, and when that side receives it, spawns partles from the given list or stream.
some things about that are,
*how to easily configure where that data will be sent
*find possible performance issues
*find possible security or abuse issues
-
I intended on making this a bump of an old microprocessor thread. I can't actually find it now, but it involved little 'components' which run seperately and are duplicateable. e.g. I make a not gate and then it has pscn and nscn which exists in my main simulation, and when i want i can copy it to other places... its compicated
