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 - jwalker
Pages: 1 ... 13 14 [15] 16 17 ... 45
211
« on: August 26, 2012, 06:54:35 pm »
TI Bug report:
So I was testing some form stuff that involved the fullscreen paramater. I made a form that would be fullscreen and visible to the user when they opened the script, when on.construction is called. I closed that script and came back later and reopened it and got an error stating that function 3 of drawRect had to be >= 0, it was located in the form drawing code. I tried it on the calculator only to have the same outcome! I also noticed that on the student software if you just set the script again right after the error it worked just fine. So I changed the fullscreen paramater to false and then closed and reopened the script only to find out that platform.window.width and platform.window.height returns a 0 when initialy running it. Initialy bieng when you open it, not when you reset the script on the student software.
212
« on: August 26, 2012, 01:55:00 pm »
Very Nice, trying it out right now
213
« on: August 25, 2012, 04:07:39 pm »
Here is another update:
This version *should* be unicode compatible, I changed all of the string.sub's to string.usub, and I already used string.split.
This version also sees a change to buttons, they now send two arguments to the click callback function, the buttons handle and its parents handle.
I also added a form_name:removeControl function whos parameter is the controls handle.
All parameters are the same as the last release last night.
214
« on: August 24, 2012, 08:09:10 pm »
I believe the bug when you resize the window is now squashed.
Here is the new versions of the file,
the .lua one is for 3.1, and the .tns is for 3.2.
This does not require the libs.
Also, does everyone think that the size of the text needs to be bigger, if so tell me.
The only reason I havent made it larger yet is because of space problems that I think exist.
Also if you do run the script there is a little utillity that tells you how much memory is being used by lua.
paramaters:
window = --dont need
form = x, y, width, height, fullscreen, title, titlecolor, bordercolor, isdrawn, contextmenu, cmtable, hassb, hasicon, iconimg, draggable
dialog = x, y, text, title, backcolor, titlecolor, bodytextcolor, isdrawn
button = text, x, y, action, txtcolor, bgcolor, parent
lable = x, y, text, txtsize, color, parent
textbox = x, y, width, text, textcolor, tbcolor, parent, selected
radioButton = text, x, y, marked, backcolor, markcolor, txtcolor, parent
contextm = --dont need
checkbox = x, y, text, checked, backcolor, checkcolor, textcolor, parent
pb = x, y, width, height, labeltbl, picturetable, txtcolor, index, lablename, parent, selected
NumericUD = x, y, num, linecolor, maxnum, minnumber, textcolor, pmbcolor, parent, selected
tabcontrol = x, y, width, height, tabtable, parent
listbox = x, y, tabval, selected, scrollbars, parent
toggle = x, y, state, parent
inputDialog = x, y, text, title, backcolor, titlecolor, bodytextcolor, isdrawn, btnAction
cant use: scrollbar, progressbar, statusbar
If there are any questions, please ask!
215
« on: August 21, 2012, 11:48:30 pm »
Realy It depends on what you want to do. Personaly, I do both and own an Nspire CX, Nspire clickpad and a Prizm.
The Nspire CX is great for math and playing games (when not locked down) that are written in C/ASM. Lua is also a very easy to learn language and you can make games with it. It also has alot of memory, you can store several doom wads on it.
The prizm is an open platform, so your games written in C/ASM probably wont be blocked. The switch to the prizms interface from a TI one is kind of hard. The math features are deffinately similar to that of a TI-84+, like Art said.
216
« on: August 21, 2012, 12:44:32 pm »
So today I realized that in about two months (the end of october) it will have been a year since I started Development on this project, and it has come a long way since then. 
217
« on: August 21, 2012, 10:21:52 am »
You can make 3.2 programs completely compatible with 3.1 ones
Oh I meant for example if he decided to use the 3.2-only physic engine or commands. On the TI-84+ I remember people tried to make their games 83+ compatible, but some others forgot that the 83+ had no clock, so people complained that their games won't send to a 83+ because it uses the clock.
That would make it incompatible, so would using withGC. But since he is using 3.1, He shouldnt have to realy worry about anything other than using setAlpha, platform.gc, the clipRect command "intersect", and there may be a few others and I just dont remember them. Those commands that I just listed will not work on OS 3.2
218
« on: August 20, 2012, 05:59:06 pm »
Wow, its progressing fast...
219
« on: August 20, 2012, 01:55:14 pm »
So here is where Im at, on using TI-Basic anyway...
Currently I allow it to create forms, make them go full screen, make them move and allow them to go from fullscreen back to normal.
But before I realy continue this Idea, I need to get an idea of what this could be used for...
220
« on: August 20, 2012, 12:26:17 am »
You can make 3.2 programs completely compatible with 3.1 ones
221
« on: August 19, 2012, 07:08:39 pm »
Thanks I see how that works... This may be an interesting project...
222
« on: August 19, 2012, 04:11:35 pm »
I think that may be it too, but maybe he found something we dont know about...
223
« on: August 19, 2012, 04:00:55 pm »
Now just how to figure out the best way to make a graphics context for forms...
224
« on: August 19, 2012, 03:57:03 pm »
I think that classes use setmetatable...
I could be wrong though
Yes, I know, that's why I mentioned it. We can't port classes until it is integrated.
I wonder how they got away with out having to use metatables, as they are used quit a bit.
225
« on: August 18, 2012, 09:54:48 pm »
Nice, what kind of things do you plan on makeing?
Pages: 1 ... 13 14 [15] 16 17 ... 45
|
Show Posts