Author Topic: Features Wishlist (Read 687109 times)

Quigibo · « **Reply #960 on:** July 18, 2010, 02:52:57 am »

Nope, the LCD is so slow that if you try to write that data any faster than its slow speed, it causes weird graphical glitches. Its more efficient to have the routines in 6MHz because then I don't need to add as much extra pausing code. Even the 4 level grayscale that calc84maniac wrote was too fast for even 6MHz so I still need pauses, just not nearly as many as I would in 15MHz mode, so you end up with a routine that takes less memory.

Magic Banana · « **Reply #961 on:** July 18, 2010, 03:04:11 am »

Oh, that explains it. That's too bad, I could really enjoy the speed of 15mhz with grayscale graphics, but I guess I have to settle with monochrome for speed. While on the subject of grayscale, how much slower does adding extra shades of gray make drawing? Like going from 3 -> 4 or even other numbers such as 4 -> 5 and 5 -> 6?

Quigibo · « **Reply #962 on:** July 18, 2010, 03:25:02 am »

All the routines are almost exactly the same speed since they are limited by the LCD speed rather than the CPU speed. Even if I were to write an 8 level grayscale routine, odds are, it would be just as fast as the 4 level or the 3 level or the monochrome. The only speed you would be gaining from monochrome is that you don't have to update the LCD as often.

Magic Banana · « **Reply #963 on:** July 18, 2010, 03:44:00 am »

Really? Interesting, I always that that it took more to draw out grayscale, with the buffers and all. So, if I were to run a program at 15Mhz, but clock it to 6Mhz when drawing, would there be a significant change in speed, or is it the drawing itself that slows the programs down so much?

Quigibo · « **Reply #964 on:** July 18, 2010, 03:50:24 am »

Yeah, its the drawing itself since you're drawing twice as many sprites, each one to 2 buffers.

Darl181 · « **Reply #965 on:** July 19, 2010, 04:16:31 pm »

New request.
When ReturnIf is called, it would be nice if the Fix tokens were taken care of automatically.
Say the person called Fix 3.
ReturnIf could do the Fix 2 on its own.

nemo · « **Reply #966 on:** July 19, 2010, 04:16:35 pm »

Darl181 has a neat idea in the Your Projects Post and Critique thread. his idea is to have the statement ReturnIf (and presumably Return!If) automatically set Fix # statements to their defaults. So if in a program you had Fix 1 at the beginning, if you had a ReturnIf statement, the program would automatically set Fix 1 (large sized fonts) back to Fix 0 (small sized fonts). this way you wouldn't need to use If (EXP):Fix 0:Return:End.

ninja'd by himself.

calcdude84se · « **Reply #967 on:** July 19, 2010, 04:18:23 pm »

That might not work, since you wouldn't want those flags reset every time you returned from a subroutine. Better is to do as I suggested (in the same thread), or possibly have a token that adds the equivalent of this code automatically.
Automatic cleanup would be nice in any form, though.

Darl181 · « **Reply #968 on:** July 19, 2010, 04:25:24 pm »

Beat you to it

Four seconds!? wow

The return descriptions confused me for a bit.
I think I'll print out that part of the thread and put it in my binder with my commands list.

Magic Banana · « **Reply #969 on:** July 19, 2010, 06:44:35 pm »

Hmm, I guess what they would be looking for would be a 'reset to default settings' kind of action, which would actually be really interesting actually. Maybe have a number (not sure if all of them are taken already) which resets all of those text and drawing commands to the TIOS default so that instead of remembering what you changed and then putting a bunch of Fix # and hoping you got them all so instead of putting a combination of Fix 0 Fix 2 Fix 4 Fix 6 Fix 8, you could just have Fix 10 (or something) to make sure that all of them are default.

I guess you can always make it part of ClrHome as well, seeing as the only reason you call it is when you are closing the program.

Quigibo · « **Reply #970 on:** July 19, 2010, 06:45:23 pm »

@Darl That would be a huge inefficiency, but you did remind me of the fix extender idea that I forgot about. You can reset all the fix modes at once by chaining them together like "Fix 0246" for instance to set modes 0,2,4, and 6 in a single line of code for convenience. I might have time to add that next release.

Also another feature I will be adding is "Temporary Pointers" which are similar to static pointers. For times when you only need to use some data exactly once, you will be allowed to do things like Pt-On(X,Y,[0123456789ABCDEF]) to both create the data in memory and return the pointer to that data in a single line. Its just as efficient as regular static pointers but has the advantage of not taking up any extra pointer names so you are less limited by the 150 name limit. This also will apply to Strings, Data(), and the Zeros() commands which can also be used to return temporary pointers.

calcdude84se · « **Reply #971 on:** July 19, 2010, 07:15:47 pm »

Cool. We can already use it with strings for Disp, but a more general application will be nice. Fix extender could be useful too, even though it only saves source code space.
As for automatically resetting flags on exit, my idea was to have the program start with

Code: [Select]

sub(M
Fix 0
Fix 2
Fix 4
Fix 6
Return
Lbl M

which would automatically reset them on exit. (Or create a dedicated token for this)

Tribal · « **Reply #972 on:** July 19, 2010, 09:54:38 pm »

Would it be possible to specify multiple arguments for 'Fix' say using a comma to separate each one?

DJ Omnimaga · « **Reply #973 on:** July 19, 2010, 10:40:41 pm »

Quote from: Quigibo on July 19, 2010, 06:45:23 pm

@Darl That would be a huge inefficiency, but you did remind me of the fix extender idea that I forgot about. You can reset all the fix modes at once by chaining them together like "Fix 0246" for instance to set modes 0,2,4, and 6 in a single line of code for convenience. I might have time to add that next release.

Also another feature I will be adding is "Temporary Pointers" which are similar to static pointers. For times when you only need to use some data exactly once, you will be allowed to do things like Pt-On(X,Y,[0123456789ABCDEF]) to both create the data in memory and return the pointer to that data in a single line. Its just as efficient as regular static pointers but has the advantage of not taking up any extra pointer names so you are less limited by the 150 name limit. This also will apply to Strings, Data(), and the Zeros() commands which can also be used to return temporary pointers.

Nice ideas, especially the pointers one. I always wished I could do stuff like Text(0,0,"HI PEOPLE", because otherwise it can be a bit annoying to have to store text to pointers just to use it in the title screen options, for example.

calcdude84se · « **Reply #974 on:** July 20, 2010, 10:57:06 am »

Tribal: Above, Quigibo mentioned that he plans (or will consider planning) to allow chaining them like Fix 0246, which is even better than using commas.

Author Topic: Features Wishlist (Read 687109 times)

Quigibo

Re: Features Wishlist

Magic Banana

Re: Features Wishlist

Quigibo

Re: Features Wishlist

Magic Banana

Re: Features Wishlist

Quigibo

Re: Features Wishlist

Darl181

Re: Features Wishlist

nemo

Re: Features Wishlist

calcdude84se

Re: Features Wishlist

Darl181

Re: Features Wishlist

Magic Banana

Re: Features Wishlist

Quigibo

Re: Features Wishlist

calcdude84se

Re: Features Wishlist

Tribal

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

calcdude84se

Re: Features Wishlist