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 - calcdude84se
Pages: 1 ... 105 106 [107] 108 109 ... 161
1591
« on: July 24, 2010, 10:18:22 pm »
oh, wow  But yes, it'd be totally worth it  I agree, this'd deserve a POTY award, especially if you get some compression in there.
1592
« on: July 24, 2010, 09:54:03 pm »
but right now you could only do 25 seconds... That's more than enough, actually... 
1593
« on: July 24, 2010, 09:20:51 pm »
Nice, the demo sounds awesome. (Your recording, I don't have a converter) Too bad for the complete lack of compression (That won't fit on on 83+ and not an 84+ either IIRC) Interesting to see where you'll take this. Good luck! 
1594
« on: July 24, 2010, 07:36:05 pm »
The problem with normal screenshots is that they require the calc to be receiving keys like on the homescreen (which means not during programs, etc.) My solution was a custom interrupt, but they can often get messed up by other things, and it reserves the link port. The 84+(SE) has a hardware setting to send the screen automatically through USB. What do you mean by linking tests? And if you're saying that won't work, how do you plan to get screenshots? Just asking
1595
« on: July 24, 2010, 05:26:02 pm »
The tokenInfo struct was intended to simply hold enough data for the tokenization routine. If you wanted to store information in a text file, the structure would be more like an alpha-sorted sequence of strings with the corresponding information (one- or two-byte, the token hex). Actually, if you chose the format appropriately, you could make it user-editable, like this: (this is only a suggestion, you can probably come up with a better format that does the same) (also, note that I don't know the hex for any tokens, so it's made up) Disp
*45
Output(
*84
GarbageCollect
BB68
sin(
*97
OpenLib(
82d2Note that you'd have to alpha-sort it at the beginning of the program (probably temp-only), but it would make it user-editable
1596
« on: July 24, 2010, 03:46:11 pm »
I don't have much experience with hooks, but wikiti can be useful here.
For those and interrupts that stay alive after the setup program ends (it might have to be an app, I'm unsure), you'll definitely have to write it in ASM. (Especially because drawing the image will involve writing directly to the LCD)
AFAIK, a hook is just a routine the OS calls before it does a certain thing, like get a key, for example. These are pretty simple to set up (writing somewhere in RAM or maybe a bcall)
As for the interrupts, yeah, you'll probably end up with a hook (especially if it's an app). But if it's a program, then the basic idea is to use some saferam (like appbackupscreen or statvars) to store the code for handling the interrupt and most likely for the entire routine as well.
1597
« on: July 24, 2010, 03:39:21 pm »
It might be possible, but the best way would be to install a custom interrupt (or something more permanent, like a hook to enable said interrupt, because custom interrupts get killed often) to draw the image behind every space character on the home screen. (With possible exceptions for the current line) When I have some time, I'll look into how practical this could be Edit: A possible problem that comes to mind is that the hook might not be enabled during a program, if that's important. But I'll look into it.
1598
« on: July 24, 2010, 03:35:45 pm »
lol. I've never really seen anything, sadly  I hope to eventually.
1599
« on: July 24, 2010, 02:39:15 pm »
Hm... First of all, you probably don't need to make the method recursive.
I'd suggest an approach of looping through the string with pointers rather than making it recursive and copying the string every time.
Secondly, you probably shouldn't be using strpbrk() to move to the next token, rather, using a looping method, you should just advance the pointer manually to the next token.
So, some C: (I'm assuming the existence of some external functions and some pre-existing variables and memory locations)
tokenInfo findToken(*char string); /*Given a string, this should find the longest token and return its length and hex*/
typedef struct {
size_t chars; /* How many chars are in the string making up the token */
BOOL twoByteToken; /*Whether or not the token is two bytes*/
byte hex[2]; /*the two bytes making up the token, or only hex[0] if it's a one-byte token*/
} tokenInfo;
/*Working from these two...*/
void tokenize(*char string, *byte buffer) { /*Takes a string and a buffer to store generated hex. Make the buffer dynamic on your own time. (Or ask me ;D) */
tokenInfo currentToken;
while(*string != '\0') {
currentToken = findToken(string);
*(buffer++) = currentToken.hex[0];
if(currentToken.twoByteToken)
*(buffer++) = currentToken.hex[1];
string += currentToken.chars;
}
}Would something like this work?
1600
« on: July 24, 2010, 01:22:01 pm »
On topic, any progress lately? How's it been going?
1601
« on: July 24, 2010, 01:03:31 pm »
Cool! You know how much we love screenies Can't wait to see it in action!
1602
« on: July 24, 2010, 01:02:04 pm »
I think that's a little off * calcdude glances at key 41, which is the [ON] key Except for the [ON] key, which doesn't have a key code (it is the [ON] key), that's correct. Good luck!
1603
« on: July 24, 2010, 12:58:58 pm »
Looks awesome! I do hope you have the physics right, because otherwise it might be impossible to solve level 11 Good job, though. Keep up the good work!
1604
« on: July 24, 2010, 12:55:35 pm »
Interesting... The main problem is getting the screen, though. You have several options here: The non-USB calcs will have to do communication through the link port, which means programs can't use it, not to mention you'll need a custom interrupt that can't be touched, so programs can't use their own unless it get's chained to yours. The USB calcs can do as above, or, because the USB hardware has a mode (used for the TI-Presenter, but it can be re-used for your purposes) that'll automatically send the screen, you can use that. You still can't touch the USB port. It'll be interesting to see you get it work on the 83+(SE)... But good luck!
1605
« on: July 24, 2010, 12:19:45 pm »
Qazz, he said it was in the case Shmibs, that is surprising. The only way it might not do this if the program is executing bcall(_getKey) (like how keys work on the homescreen, with 2nd and alpha not returning), or if you get lucky with the checksum (very unlikely) Very interesting...
Pages: 1 ... 105 106 [107] 108 109 ... 161
|
Show Posts