Replying to:
GuzzlerReally cool! I have a suggestion: In Zsketch, use GLINE instead of GPSET(or whatever you are doing to get little dots). So your code would look something like this:
WHILE TRUE
CLS
OLDX=X
OLDY=Y
GLINE OLDX,OLDY,X,Y
VSYNC 1
WEND
I don't think using WHILE is a good idea. It's hard to find the loop when editing the program. I think @Lable is much more visible.
Replying to:GuzzlerReally cool! I have a suggestion: In Zsketch, use GLINE instead of GPSET(or whatever you are doing to get little dots). So your code would look something like this:
WHILE TRUE
CLS
OLDX=X
OLDY=Y
GLINE OLDX,OLDY,X,Y
VSYNC 1
WEND
CodeTrooper, it was just an example.
Replying to:GuzzlerReally cool! I have a suggestion: In Zsketch, use GLINE instead of GPSET(or whatever you are doing to get little dots). So your code would look something like this:
WHILE TRUE
CLS
OLDX=X
OLDY=Y
GLINE OLDX,OLDY,X,Y
VSYNC 1
WEND
When no one notices your previous comment:
Spoiler
You need to connect the previous frame's touch x and touch y to the current touch x and touch y with gline. (in zsketch)
bug: on the old 3ds if you open a window and click the check or the X it will continuously flash. works great on n3ds though
Replying to:
A2D_appsbug: on the old 3ds if you open a window and click the check or the X it will continuously flash. works great on n3ds though
Yeah, unfortunately, it's not very optimized for the old 3ds. There's probably some more optimization that can fix things like this, but I'm not sure it will ever be fully optimized for the old 3ds.
Replying to:A2D_appsbug: on the old 3ds if you open a window and click the check or the X it will continuously flash. works great on n3ds though
Ok now it doesnt work at all. I downloaded it twice and ran zos but it crashes EVERY time now
Replying to:A2D_appsbug: on the old 3ds if you open a window and click the check or the X it will continuously flash. works great on n3ds though
That's very odd. Can you find the details of the error? A lot of people have been reporting crashes, but I haven't been able to actually replicate any of them.
This is a very late response, but it still counts :P
Replying to:A2D_appsbug: on the old 3ds if you open a window and click the check or the X it will continuously flash. works great on n3ds though
I open it and it crashes.
Replying to:A2D_appsbug: on the old 3ds if you open a window and click the check or the X it will continuously flash. works great on n3ds though
probably just an error w/ the passwrd, does it send you to the homescreen or ends the program?
Replying to:A2D_appsbug: on the old 3ds if you open a window and click the check or the X it will continuously flash. works great on n3ds though
I run it and it closes the program instantly
i'm trying to make my own version of a multitasking os, but i get stack overflow galore :D
Replying to:
PtcguyOn o3ds, everytime I log in:
Subscript out of range in 0:200
and some illegible text that is on the desktop.
EDIT: If I change line 199 from
FOR I=0 TO LEN(DDAT$)-1
to
FOR I=0 TO LEN(DDAT$)-2
it works but everything flashes and is mostly unusable.
i get the same results. (n3ds and o3ds,)
Spoiler
{i can switch to o3ds clockrate using homebrew}
Replying to:PtcguyOn o3ds, everytime I log in:
Subscript out of range in 0:200
and some illegible text that is on the desktop.
EDIT: If I change line 199 from
FOR I=0 TO LEN(DDAT$)-1
to
FOR I=0 TO LEN(DDAT$)-2
it works but everything flashes and is mostly unusable.
I swore I fixed this. Did you download the update?
Replying to:PtcguyOn o3ds, everytime I log in:
Subscript out of range in 0:200
and some illegible text that is on the desktop.
EDIT: If I change line 199 from
FOR I=0 TO LEN(DDAT$)-1
to
FOR I=0 TO LEN(DDAT$)-2
it works but everything flashes and is mostly unusable.
Mariominer: I'm on the latest update. I just redownloaded to confirm.
Replying to:PtcguyOn o3ds, everytime I log in:
Subscript out of range in 0:200
and some illegible text that is on the desktop.
EDIT: If I change line 199 from
FOR I=0 TO LEN(DDAT$)-1
to
FOR I=0 TO LEN(DDAT$)-2
it works but everything flashes and is mostly unusable.
That's odd. I made that update that specifically fixed just that. I'm not experiencing any of the issues that are being reported though, so I'm not sure why.
A way you could make this optimized for the O3DS is by making the windows fullscreen only.
Replying to:
chickenA way you could make this optimized for the O3DS is by making the windows fullscreen only.
That could actually work. It would take a complete redesign of the operating system on o3DS though. Plus it could only run one thing at a time, which still technically fulfills the goals that I set for this technology (being able to report back to the operating system while running a program), but it still is a bit more work. I'll try when I finish my current project.
