This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Xeda112358
Pages: 1 ... 59 60 [61] 62 63 ... 317
901
« on: June 20, 2013, 09:10:38 am »
Hmm, so what is actually going on in that screen? Is it that half of it is displayed to the user while the other half is some kind of backup?
902
« on: June 20, 2013, 09:03:26 am »
Label jumping is the plan, as well as jumping from the top to the bottom. Last night in HCWP, I was fairly productive and tested a bunch of things including the font and making certain tokens invisible (like Then and End tokens). I also adjusted the indent to be more logical. Today I want to try to make some "token hooks" for the other languages and try to get it so that you can move through the source and possibly edit code.
For menus and otherwise accessing tokens, I hope to make it similar to TI-BASIC, but with a few changes. So you can still access the drawing commands by pressing [2nd][prgm], and the order will be basically the same. However, I might add in some pages to the math commands, and for token sets like those for Celtic 3, Omnicalc, and others, more menus will have to be placed somewhere. As well, I plan to have a more organised catalog.
EDIT: Forgot the screeny with invisible tokens.
903
« on: June 19, 2013, 09:13:32 pm »
For the purpose of testing I started the BASIC program editor. As it currently is, I have all of the 1-byte tokens added and some 2-byte tokens. I tried not to change anything except to fix up some issues with the BASIC tokens. In particular, pic variables, matrix, Str, GDB, and list variables that are hacked now have actual names. The way I designed the token system, it is possible to use code in place of a token string, so they do not have huge LUTs. Instead, just a simple code that handles each of those. So for example, the 255th hacked string is now displayed as Str255 instead of a question mark. I also made it pretty easy to handle multi-byte tokens, so I plan to add in tokens for Axe, Grammer 2, BatLib, Omnicalc, Celtic 3, DoorsCS7, and xLib commands.
(I should note that I decided to make the Editor app separate from the Grammer 3 app.)
The Grammer 3 editor will be a bit tough to create, to say the least. The BASIC editor is not taking advantage of many of the features I have already programmed into the editor, but the Grammer 3 editor will hopefully be packed with features.
I hope I didn't get any hopes up, though, because the editor doesn't do any editing yet. You still cannot choose things like the program to open, the font to use, the token set to use, the screen size, or wordwrap modes, even though those are all programmed in.
904
« on: June 19, 2013, 08:00:58 pm »
Should a topic on hook standards be made? It will require going back and forth between sites to make sure everybody is on the same page. I do think that a setup like this is very useful: AppStart:
jp Main
.db 84h,43h
jp HookInstall
jp ParserHook
jp KeyHook
jp MenuHook
...
Even if your app didn't use certain hooks, placing dummy jumps would be a good idea. This way it is very easy for other programs to run your hooks or install them. As well, making sure (as best as possible) that your hook doesn't modify inputs if it doesn't use it is an excellent idea. Then we could make some kind of appvar (or preferably a symbol variable, since it is faster to find) that simply contains a list of pages that "registered" apps can be accessed on. So if a new app wants to add itself to the list, it would need to locate the variable, augment it by 1 byte, and add its page to the list. Then any hooks would run through the app list calling their hook code from the jump table. The biggest issue would be that we would need to use the routine on another page 
905
« on: June 19, 2013, 02:05:35 pm »
Excellent post, DJ_O, I had indeed not seen a few of these or had forgotten bout them and these are all well made games. And Hayleia, congrats 
906
« on: June 19, 2013, 08:39:58 am »
tr1p1ea, this is awesome! Also, the ExecLib and OpenLib ideas are great. The problem before was that it limited programs to be used only by the 84+ calcs since those weren't available to 83+ users. But now, since programs like this cannot be compatible on older models, it makes sense to use them!
907
« on: June 17, 2013, 08:15:09 am »
At what line does it have an error?
908
« on: June 17, 2013, 07:54:22 am »
I am not sure how it is done on the nSpire, but if it is similar enough to the 68K calcs, then you should be able to do something like this:
rand(50)→temp
SortA temp
And then to access a list element, you can do things like this:
temp[1] ;retrieve list element 1
n→temp[1] ; store n to list element 1
I hope this works and helps!
909
« on: June 16, 2013, 09:24:44 am »
Hello imath! Where are you from? Do you have any projects?  Also, what kinds of calculators do you program for? It is great to have you here! Finally, enjoy your introductory peanuts 
910
« on: June 16, 2013, 09:22:18 am »
Well, is there any other way you had in mind? Using lists seems like the most straight-forward way. From this point, you can read list element 1, list element 2, list element 3, and so on.
911
« on: June 16, 2013, 09:18:57 am »
This is great! Congratulations on finishing this!
912
« on: June 16, 2013, 09:02:22 am »
I have never before gotten a raycaster to work, but I may have finally gotten a version to work in BASIC. It is incredibly slow, but if the code is correct, then this means I will be able to use it as a basis for converting it to other languages (like Axe, Assembly, Grammer). I know raycasters have been made many times, but I am glad to finally have made one myself How I did it: Basically, I read through a tutorial, tried to convert the C code to BASIC, failed (most likely a typo) then I tried it again a few days later and I made it properly (I think). I modified some of the code to optimise it for speed, I made some inputs as constants, and I made the viewing direction based on an angle measure instead of a vector. So essentially, there are three inputs-- the player (x,y) coordinate in the map and the angle at which they are turned. Also, the map data is stored in the last 31 columns of pixels on the graph screen. I am pretty sure that there is still something wrong with the code, but I will try to work that out. As an example of what seems to be going wrong, if the viewing angle is 270 degrees (down) it seems that the rays only sweep from 270 degrees to about 315 instead of 225 to 315.
913
« on: June 15, 2013, 02:06:21 pm »
5298 : You use OmnomIRC to make sure you don't double-post
914
« on: June 15, 2013, 08:25:50 am »
Wow, that is a really neat way of handling water!
915
« on: June 14, 2013, 01:47:00 pm »
Well, to be honest, the 83+/84+ series has had the possibility of a third-party CAS for a long time and it hasn't been done yet, so they probably aren't too worried.
Pages: 1 ... 59 60 [61] 62 63 ... 317
|
Show Posts
