BotOS - A open project!

[Tasuit]

So far, yes
Rich: Yes this is based of our roleplay on the server, so you can build different things with the modules, but on build it would just be spawning.

[BlackholeWM]

Could you add thrust outputs to the bot, and could you modify the variables to control them?

If you did this:

name BotOS Build 0002
@inputs IOBus:vector GBus:wirelink
@outputs Bus1 ForwardThrust LeftThrust RightThrust
@persist A B C D
@trigger all
runOnTick(1)
#runOnTick(1) is always useful.
#Basic Data Allocation for screen#
# GBus = Screen
# IOBus = First Module
# Bus1 = IOBus Output
######################
GBus:writeCell(2042,9)
GBus:writeString("Build 0001",20,0)
######################
######################
#Here comes the first subroutine#
if (IOBus:w()) {SetVariableProgram=1}
if (SetVariableProgram) {
    GBus:writeString("Writing Thrust Variables",0,1)
    A = IOBus:x()
    B = IOBus:y()
    C = IOBus:z()
    if (IOBus:w() == 1 & SetVariableProgram == 1) {Bus1=1, GBus:writeString("Done, Waiting for Respond",0,2)}
    if (Bus1==1 & IOBus:w() ==0 ) {SetVariableProgram=0, GBus:writeCell(2041,1), Bus = 0}
}
ForwardThrust = A
LeftThrust = B
RightThrust = C

Then a dance module could be:

name BotOS Dance Module
@inputs Bus1 Active
@outputs IOBus:vector
@persist Time
@trigger all
interval(1000)
if(Active & clk()) {
Time += 1
if(Time == 1) {
IOBus = vec4(1,1,-1,1)
}
if(Time == 2 & Bus1) {
IOBus = vec4(-1,-1,1,1)
}
if(Time > 2 & Bus1) {
Time = 1
}
}
else{ IOBus = vec4()
Time = 0 }

Or something similar.

I know the main chip's thrust outputs could simply constantly update to match the input but as you said this will be customizable, and maybe people will have a need for the more complex method.

[BlackholeWM]

Has this been dumped already?

[Tasuit]

This has not been dumped, but as i mentioned in the first post i was going to sweden for a week, and i am now back to work..

[Asphid]

Every time I see this thread, I get a little freaked out. My last name is Botos. It's Hungarian =D

[Tasuit]

Oh shit, what a coincidence!.
Well, i have been thinking about changing the name
But let me just finnish it first ^^

[Eirath245]

An alternative (and possibly less confusing) way of emulating subroutines would be to have a single string variable "Current Subroutine".

This way, instead of being

if(something){somesubroutine = 1}
else {anothersubroutine = 1}

if(somesubroutine) {dosomething}
if(anothersubroutine = 1) {dosomethingelse}

You could do:

if(something) {CurrentSubroutine = "Something"}
else {Current Subroutine = "SomethingElse"}

if(CurrentSubroutine = "Something") {DoSomething}
if(CurrentSubroutine = "SomethingElse") {DoSomethingElse}

Which (at least to me) is less confusing, and prevents you being overwhelmed with variables.

You could also use it to debug, by simply saying:

#debugging subroutine
GBus:writeString("CurSubroutine: " + CurrentSubroutine,?,?)

Writing the current subroutine being executed onto the screen.

[Tasuit]

What your doing is flipswitch variables, they seem a little less confused.
I will try and implent the string idea, but the current subrotuin method is the easiest in my opinion

[rich_27]

Why not just use:
if(Something){SRout=1}
elseif(SomethingElse){SRout=2}
else{SRout=3}

if(SRout==2){code}

etc...
Then you wouldn't have to bother with strings.

[Tasuit]

Rich, Because with strings we can debug it much easier