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 ... 16 17 [18] 19 20 ... 45
256
« on: July 18, 2012, 12:57:27 pm »
I all ready implement a screen manager, it just looks a little diffrent from yours because it considers every form a screen, and has to switch between the forms.
What I mean is that say I have something like form:paint(gc), which is already there, everytime it is called to repaint the form, it would call something like form1_paint(gc), giving WZ its own 'events'.
The toggle switch is on the very bottom of the class definitions in the last file that I uploaded, I have some creation code commented out.
It looks like:
--toggle test 0.1
--t1 = toggle(50, 100, true, form1)
--t2 = toggle(1, 1, false, Tabs.atab)
thanks for the link to your scrollbars class, I think it will help.
257
« on: July 17, 2012, 08:28:20 pm »
Does anyone know the best way to implement scroll bars? I was thinking about how to do it, but im not quite sure how to calculate when the scroll bars gets larger and smaller depending on what is in the scrollable area.
Also for those who tried the dev release/preview, what did you think about the toggle switch, if you noticed it?
258
« on: July 16, 2012, 10:01:08 pm »
well now you just have to pay $15, you know for a touchpad keypad, instead of $60.
Wait, the touchpad will work on that one? 
they actualy have a touchpad that is the color of the calc, light blue
259
« on: July 16, 2012, 07:43:56 pm »
well now you just have to pay $15, you know for a touchpad keypad, instead of $60.
261
« on: July 15, 2012, 11:55:00 pm »
wow, thats not good
262
« on: July 15, 2012, 11:32:49 pm »
yup
263
« on: July 15, 2012, 10:44:31 pm »
No, it is a CAS device, so you can not interchange keypads
EDIT: here is the picture:
264
« on: July 15, 2012, 09:28:16 pm »
all of the keypads interchangable, but the clickpad only comes in a light blue.
specs that may matter:
light blue: Memory: 20 MB storage memory / 16MB operating memory
dark blue: Memory: 15 MB storage memory / 32MB operating memory
265
« on: July 15, 2012, 08:53:57 pm »
no TI-Nspire CAS dosent support removeable keypads, the 2nd one is a darkblue and white, like the regular CX, but with the aircraft carrier body style.
If you are getting an actual clickpad keypad, it dosent realy matter
266
« on: July 15, 2012, 08:39:54 pm »
1. The Origional Light blue Nspire or the 2nd version, which is dark blue.
2. IDK, I own a light blue one, but since the clickpad is light blue, it will fit with the light blue calc.
3. not much realy, a good calculator
267
« on: July 15, 2012, 05:37:11 pm »
Excuse my double post...
I am happy to announce that I hav successfully got the 'lib' system to work.
Currently, I have only moved the paint code to the lib, but I will move the rest later.
This is a proof of concept release, it is a v3 development version.
I tested these two files on both the computer and my old light blue greyscale nspire.
What this could allow is:
Easily create styles for WZGUILIB.
Easily switch styles durring execution.
Editing how the GUI objects look and work on calc (great for me and style developers).
Allow multiple styles on one calc without having to have several diffrent versions of WZGUILIB.
*Allow to only have some class code loaded.
Questions and comments are definately welcome
**********************How to set up**********************
send both files to your calc
place WZ_ST_LIB.tns inot your MyLib folder
Refresh your libraries
execute WZ_LibTST
*I havnt yet implemented it.
268
« on: July 15, 2012, 02:39:16 pm »
I have been so busy for the first two months that I havnt had alot of time to do other stuff, Although I think I will get more time in about 2 weeks or so
269
« on: July 15, 2012, 12:13:37 pm »
So I had a thought about something that I may do.
I havent realy been able to test out the style system that I proposed, although today I may get Time, but this idea could go hand in hand with it.
What I was thinking about doing was hidding the main events that drive WZ (on.click, on.paint, etc...), and do this instead:
--create a window in on.create, which will still be 'visible' to the user
window = form(...)
--then after on.create we would have the new 'events'
window_paint(gc)
window_click(x, y)--where x and y is the location of the pixel in the forms body
window_etc.....
all controls would also work similar, so it is kind of like VB.net, or C#.
I thought that this could be released in a WZGUILIB_EventDriven stylepack, or maybe it could be integrated into all WZ versions, although that would be a more radical aproach.
270
« on: July 12, 2012, 12:29:12 am »
They are, what Im trying to do is get them just right, so they arent to big, and they arent too small. They have to be just the right size so they can fit in areas other than just forms. I think if I make them just a little bit bigger it might be the right size.
Pages: 1 ... 16 17 [18] 19 20 ... 45
|
Show Posts