Show Posts

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 - alberthrocks

Pages: 1 ... 31 32 [33] 34 35 ... 55
481
TI Z80 / Re: Axe GUI Library
« on: June 03, 2011, 03:23:02 pm »
Oh my gosh, soo many updates! :D
Since this project is getting intensely sparked, I'm going to have to get that tokenizer working! :) (Basically, converting Michael_Lee's tokenizer to modular form)

482
TI Z80 / Re: zStart - an app that runs on ram clears
« on: June 01, 2011, 10:35:58 pm »
Hmm... I might use it. :) But there's one last thing.
Is there anyway I can save the screen (screenshot) to a variable, NOT the back buffer, and be able to display it again?

483
TI Z80 / Re: zStart - an app that runs on ram clears
« on: June 01, 2011, 10:16:21 pm »
Whoops, I meant L4 or L5.  In your case, I'd also suggest doing this:
Code: [Select]
Zeros(54)->GDB0
#Realloc(GDB0)
(This only works if you compile it as a program, not an App.)

L5 would work if you don't use Disp, Output, or ClrHome. :-\
I might be using ClrHome to... clear the screen? :P
What does the above code do? This seems to be a... wait, program writeback storage? O_O

484
TI Z80 / Re: zStart - an app that runs on ram clears
« on: June 01, 2011, 09:47:12 pm »
Yup, only I'd use L4 or L6, as you can't run programs that use L2 from Mirage. ;)
Hm... but Axe documentation says they're evil! :P
Quote from: Axe Parser Documentation (Commands.htm in the archive)
L4 = 256 bytes (tempSwapArea) Volatility: MED (Corrupt when archiving/unarchiving in program)
L5 = 128 bytes (textShadow) Volatility: MED ("Disp","Output", and "ClrHome" will corrupt)
L6 = 768 bytes (plotSScreen) Volatility: HIGH (Any buffer drawing will corrupt)

I have to do archiving and unarchiving, so definitely not L4.
L5 is a maybe, but it seems kinda small.
And L6 is... well, impossible to use since I use buffer drawing quite a bit... :P
(Assuming buffer drawing = ClrDraw, Pxl-Change, DispGraph, etc.)

However... L3 looks OK to me, since I don't exactly... oh wait, I do use the back buffer a tiny bit to screen cap the screen, then after unlock bring it back to buffer and display it... :P
Quote from: Axe Parser Documentation (Commands.htm in the archive)
L3 = 768 bytes (appBackUpScreen) Volatility: MED (Saving to back-buffer will corrupt)

Any suggestions?

485
TI Z80 / Re: zStart - an app that runs on ram clears
« on: June 01, 2011, 09:30:50 pm »
Ah, yes, that makes sense.  If the calc APDs, then the current screen has to be stored somewhere.  This area is appropriately named the "saveSScreen."  Unfortunately for you, this is L1 in Axe.  Basically if in your program the calc APDs, then you cannot use any of L1.  Remember that Axe Vars are stored at the end of L1 (as it's actually 768 bytes if you reallocate the vars).
Here's your fix:
1. Use #Realloc() to change the location of the Axe vars to some other place, such as L4.
Heh, didn't know that was the problem! :)

So to fix, would I simply put on the top:
Code: [Select]
#Realloc(L2)...and continue to use my regular Axe variables fine, just in a different spot?
2. Never ever ever use L1 in your program.

Good luck! ;D
Oh... uhh...
* alberthrocks looks at all of his other Axe programs which exclusively use L1 :P
(not on purpose though, as you can tell)

Yep, APD stores the screen to SaveSScreen. Maybe someone should tell Quigibo to add in a bcall(_disableAPD) command.
I'm probably going to keep APD on, since it's not a bad idea to do such a thing in a lock program.

Great! Just watch Iodine, I believe it's molar mass is .01 too high because on the old table I got them from, that's what it rounded too. So I'll have to change that. You would look a little silly if you got the molar mass of something wrong :P
Nah, I'm not too concerned. My teacher doesn't really care as long as you showed your work for calculations and such. :P And besides, we've moved on to organic after the AP tests! :D

EDIT: OMG UPDATE :D :D :D zStart is DEFINITELY the swiss knife of all apps :D

486
Good luck to everyone participating in the contest! :D I will probably be staying out of this one, due to lack of time and such, especially with a trip abroad to China in the coming weeks.

487
TI Z80 / Re: Axe GUI Library
« on: June 01, 2011, 07:11:33 pm »
What about waiting until Wabbitemu can have files extracted? Oh wait, that's Windows only, yeah use Michael Lee's. I would rather compile with Axe and sending file to computer
I'm starting to wonder if you still can recall what you wrote... :P

There's no point in compiling the library itself since... well, no program is using it! It isn't exactly like an Axiom, in which you compile and then use it. In pure Axe, you include the library in the program and then compile it, which will automatically include the library. ;) (Technically speaking, our library is more like a collection of (sub)routines, but I'll leave that up to the developer to decide.)

Since we're not exactly compiling it, but rather just converting the regular text source to 8Xp, a tokenizer/detokenizer is used. That's when Michael_Lee's program enters. See where I'm going here? ;)

Although I'm hoping to get something like that done soon (this summer! :D), you're only going to see that in say, wxWabbitemu v1.5 or v2.0. There's plenty of Wabbitemu features that need to get implemented first! :P (GIF screencapping and debugging, for instance)

====
NOTE FOR OTHER PEOPLE PLAYING WITH THIS LIBRARY - do NOT use the one on the Google Code website unless it's the one in the Downloads section. SVN's copy is broken.

Also, if you don't see a mouse at all (like I did), you may need to set X and Y to some non-zero number. Add this on the top of the GUI demo program (below the header, of course!):
Code: [Select]
10->X
10->Y

488
TI Z80 / Re: Axe GUI Library
« on: June 01, 2011, 11:22:30 am »
Can't believe I didn't post here before...

I really think you guys should keep working on this. I'm playing around with an idea right now, and this would work perfectly with it. I'd also be interested in collaborating on this, if that's ok with you guys.
Oh, no problem! :) PM me your email. We have a google code site up for code hosting, but don't try to use any of the files yet... the tokenizer is broken! :P Once I get some time, I will pull down the old tokenizer and use Michael_Lee's tokenizer for the project.

Just curious - what are you planning to do? :)

489
News / Re: More online tools, this time for Nspire Lua
« on: May 31, 2011, 11:50:50 pm »
I wrote an online TNS file creator, which allows for direct input and uploads, plus it supports multiple files/input! :D
http://withg.us.to/lua2tns/MakeTNS.php

This was originally written by JayTe (MakeTNS was in Python).

I'm still working on it since this will eventually be integrated into Levak's and Adriweb's wiki (inspired-lua.org, I think), but things should be working in top notch shape at the moment! :D The only potential bug is that if someone else types a file name you used, you may end up downloading someone else's file or them downloading yours, so try to make up really random TNS file names! :P

Speaking of crappy browsers, although this isn't "compliant HTML" (it lacks a <head>, <html>, <body> - you name it!), this should work since I don't use any magical CSS... yet. No JS either. If this doesn't work in IE...
* alberthrocks bangs head on desk

490
Computer Usage and Setup Help / Re: Live CD help
« on: May 31, 2011, 11:03:49 pm »
Oh no worries, LiveCD ramdisks go poof as soon as you power down your computer or reboot it. :)
If you want a guarantee that it is gone, simply boot into your regular OS. That will typically overwrite any memory of... that LiveCD memory. :P

491
TI Z80 / Re: zStart - an app that runs on ram clears
« on: May 31, 2011, 11:01:35 pm »
Quote from: thepenguin77
1) I don't see a problem with having APD occur there. I'm pretty sure APD is interrupt based and when it quits, it quits back to the program. I have that enabled for my grayscale pictures and I haven't had a problem with APD's. Besides, I only take action if the calculator is starting up from and OFF, not from an APD.
2) What happens specifically? Because in reality, I don't even think that OS 2.43 even checks that flag. ;)

1) I can't do the bypass key because I can't check the appvar. The reason I put the bypass key in there to start with is so that you could boot your OS normally without even running any zStart code. Essentially, if you are holding [VARS], the OS jp's to zStart, sees that [VARS] is being pressed, then jp's to where the OS needs to go. In order to disable this, I would have to check the appvar first to see if the [VARS] abort should be accepted. But this completely defeats the purpose of the abort. Let's say that you have an archive glitch that is causing faulty VAT entries, even if you left the [VARS] abort enabled, you would still enter a boot loop.
Bugs
1) That's odd... for a program that I'm working on, APD seems to screw up program data. It doesn't crash, but the Axe variables are messed up. (RAM modification likely?)
2) Of course it doesn't. ;) But I think the way you display those black messages (like "Molar mass", "Confirm?", etc.) changes with setting. If you have zStart loaded, hit [On] + [-] (subtract) on 2.43 with MathPrint enabled. The message will flicker away instead of staying for a second or two. The best place to reproduce this bug is in the program menu. Assign a shortcut or startup/ram clear load program. The bug will be really apparent there.

By the way, I'm a big fan of that molar mass calc! :D AP chemistry calculations feel much better with that turned on. ;)

Feature Requests
1) Huh... VARS? I've been using [DEL] and [CLEAR] held together to bypass startup. :P
And fair enough - although it will make my little locking program terminally weak if someone knows the keys to bypass zStart. :P
Combining my locking program with zStart makes one heck of a locking program, even stronger than Krylypto... if no one knows the keys to bypass, that is.

EDIT:
2) Oh, and don't forget the ones mentioned above! :D (Especially Fast app menu/program menu and edit archived prgms and... too lazy to try to find them all :P)

492
Computer Usage and Setup Help / Re: Live CD help
« on: May 31, 2011, 10:49:38 pm »
No no no, ramdisks are NOT ram disks :P

In linux Live CDs (or DVDs, for that matter), they usually load the filesystem into the RAM so that it's faster to use, and will need the CD less. You usually can find this filesystem image as initrd on the CD. (Typically, they name it something else to conceal that name :P) Note that although you may have a ramdisk loaded, the CD is still being used, and you won't be able to eject it. Ramdisks are typically tiny little guys that spark the start of the system. They can range from 1 MB to 30 MB in size, but there's no "limit" persay.

Note that ramdisk is NOT related to general OS behavior, which is loading programs into memory and caching them for faster load times. That's why when you open something in LiveCD, it loads it from the CD, and if you close and reopen that same app, it will load pretty fast using little or no CD at all.

Hope this clarifies things! :D

493
TI Z80 / Re: zStart - an app that runs on ram clears
« on: May 31, 2011, 07:56:56 pm »
Some bugs to poke you about:

1) APD is enabled for startup programs/RAM clear programs. It should be disabled since when it turns off, bad things happen (TM). :P
2) You should prevent users from enabling MathPrint in a 2.43 OS, since doing anything top-right-display worthy will show a flicker and disappear from sight. I puzzled over that, and after disabling all the option, I narrowed it down to that little but sinister option. :P

Feature requests:
1) Allow disabling of the "bypass" key for startup/RAM programs. Yes, I know that sounds dangerous, so you are free to smash a wall of WARNING text all over my screen. :P (If you're curious, I'm working on a special little program that shouldn't be disabled :P)

494
It seems to me that the image is broken rather than the accessing of the drive itself.
Does vesamenu.c32 actually EXIST on the flash drive? If not, you can safely blame the program. :)

Download this archive:
http://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-4.04.tar.bz2

Extract this file: ./com32/menu/vesamenu.c32
(You may alternatively extract all and just grab the file from the extracted contents.)

Now copy that little guy to where the other .c32 files are, and it should work! :D
(Typically, this is the syslinux dir or the root.)

495
TI Z80 / Re: Axe GUI Library
« on: May 30, 2011, 07:16:25 pm »
Super late reply... :P I think people will use it. I've been playing around with menu code today and realized why people might use it, and am planning to implement some things (including the menu). However, some parts of it will have to be redesigned/rewritten for such uses, like for games and such :)

Pages: 1 ... 31 32 [33] 34 35 ... 55