Author Topic: Undo (Read 23369 times)

meishe91 · « **Reply #75 on:** March 01, 2011, 07:03:19 pm »

So you're storing the command number and the coordinates all in different elements in a list? What does your compressed data look like? (Like what does the data for a Pt-On(32,54), Circle(55,55,10), and Line(0,0,54,34) look like?)

Freyaday · « **Reply #76 on:** March 02, 2011, 01:26:38 am »

Pt-On(32,54) Circle(55,55,sqrt((65-55)^2+(55-55)^2)) Line(0,0,54,34) would be
{132.54, 655.55, 665.55, 400.00, 454.34}

meishe91 · « **Reply #77 on:** March 02, 2011, 02:02:52 am »

Ah ok. I think I get it now. Just to make sure you know, you know that method does limit your number of undos to as low as 499 right?

Freyaday · « **Reply #78 on:** March 02, 2011, 09:17:40 am »

Actually, If something is undone, it's list elements would be removed from the list. That means that I really do need infinite undoes. I was wrong when I typed that I only needed 999.

meishe91 · « **Reply #79 on:** March 02, 2011, 04:55:27 pm »

Why would you need to keep the command in the list if you undid it? I mean unless you're wanting to do a redo button too I don't see the point. Also, I can basically guarantee you won't get infinite undos in TI-BASIC, or really any calculator language since you're limited by memory. The only way to get more than 999 is to overflow into another list when you're done with the first.

Freyaday · « **Reply #80 on:** March 02, 2011, 08:16:21 pm »

Umm, why would I need a second list.

meishe91 · « **Reply #81 on:** March 02, 2011, 08:33:05 pm »

That's the only way you're going to bypass the 999 undo limit, unless you store to a string but then it will get really slow the bigger the string gets.

Freyaday · « **Reply #82 on:** March 02, 2011, 10:00:54 pm »

I thought strings were equally slow under all conditions, just like lists are.

AngelFish · « **Reply #83 on:** March 02, 2011, 10:01:28 pm »

Nope. Only if you access the end of a large string.

meishe91 · « **Reply #84 on:** March 02, 2011, 10:45:50 pm »

Nope, lists are the same speed regardless where you are recalling from. However strings get slower and slower the further you get into them. So say you have a string with 5000 tokens in it, it will take significantly longer to recall tokens 4951-5000 as opposed to 1-50.

Freyaday · « **Reply #85 on:** March 03, 2011, 12:31:06 am »

I didn't know that. I wonder why. On an on topic note, I'd really appreciate an explanation of your code in writing. It's hard for me to understand code, even my own, from scratch.

meishe91 · « **Reply #86 on:** March 03, 2011, 12:55:06 am »

Because TI sucks...um...wait...no...I mean...nevermind, that's what I mean

Seriously though, I'm not sure. I'm sure someone does though. Would be nice if it was uniform or just a lot faster.

And do you mean my code here for my display routine? If so, do you first understand the compression method? Because that would be a huge part of explaining the code.

Builderboy · « **Reply #87 on:** March 03, 2011, 01:03:50 am »

The reason is because tokens can either be 1 or 2 bytes long. The only way to know how long they are is to go byte by byte through the entire String until you get to the character you want, which is the source of the slowdown

meishe91 · « **Reply #88 on:** March 03, 2011, 01:04:44 am »

Oh ya...that's right. I remember Hot_Dog saying something about that in the Correlation sub-forum somewhere.

Freyaday · « **Reply #89 on:** March 03, 2011, 01:10:07 am »

Actually, I meant the Braille on the wall next to me.

Yes, I am referring to your code posted there, Mr. Builderboy. And no, I can't get my brain to process any of the code. It keeps freaking out.

Author Topic: Undo (Read 23369 times)

meishe91

Re: Undo

Freyaday

Re: Undo

meishe91

Re: Undo

Freyaday

Re: Undo

meishe91

Re: Undo

Freyaday

Re: Undo

meishe91

Re: Undo

Freyaday

Re: Undo

AngelFish

Re: Undo

meishe91

Re: Undo

Freyaday

Re: Undo

meishe91

Re: Undo

Builderboy

Re: Undo

meishe91

Re: Undo

Freyaday

Re: Undo