What is the cause of the line being cut off at the right side of the screen?

What do you mean ? Do you mean that it gets clipped before reaching the edge of the screen ?
Well that is because I put a wrong number
Same for what happens at the bottom
I put 62 and 94 instead of 63 and 95, but that is not really difficult to change

Tried my hand at it
Sorry, not in vectors but in png.

edit new version with longer things at the bottom

It is indeed signed, but not treated as integers. Normal multiplication, on the other hand, works for any type of integer (signed or unsigned).

Ah. Yeah, I see it now in "the low byte as the decimal part" o.o°

But now that I changed all the ** and // into * and / in my program, it is worse

Hello everyone, as the title says, I need a clipped line routine (I mean a routine that still draws the line even if it is partly off-screen) that I can call with LINE(X1,Y1,X2,Y2) or that would use X1,Y1,X2 and Y2 as variables (there roles in the routine being obvious).

I saw this one by Darl181 but it is not a routine that I can call with LINE(X1,Y1,X2,Y2), it is a full program that includes line clipping, but only supporting one point and the other one always at the center

Then I saw this and tried to write it myself but failed miserably.
Here is the source in the spoiler if you see where the error is (note that it fails even though it is not optimized, I coded it noob-style to be sure that it would work but still failed )

So, anyone has a solution ?

Because the teacher said you can't use an Nspire. Remember, although students buy graphing calculators, it's teachers that they advertise to. (Which means that free market economics doesn't apply to graphing calculators, which is why they're overpriced.)

That is true. This is also why so many people in France buy 82Stats.fr, because this is the one teachers talked about even though the 76.fr does the same for cheaper and the 83+ is far better (not even talking about the 84+).

Any ideas why Vogtinator's video got so many dislikes?

I think they come from people who don't follow the Linux portage to the Nspire. Some might think it is fake, others might think that there is a typo in Linucx.

I believe I'm a Coder of Tomorrow because from time to time I think of a great idea that's probably gonna be a revolution, and I say to myself "Maybe tomorrow (read : a lot later)".

I said the exact same thing in my introduction

I'm a coder of tomorrow because each time I have a program idea, I think "maybe tomorrow I'll code it".

Anyway ! Great to see French people invading Omnimaga
Welcome here, have some more of those and enjoy your stay ^^

Quote from: Hayleia on November 12, 2012, 01:00:53 pm

Quote from: squidgetx on November 12, 2012, 12:50:21 pm

How could chickendude not know about chickens?

Lol, didn't think about that one

Quote from: squidgetx on November 12, 2012, 12:50:21 pm

I'm not sure how TinyCraft's mapper works, but the fact that it uses 8x8 tiles gives it a huge advantage over anything that I can come up with right now. 8x8 tiles are fast and flexible, making it easy to build a grayscale redraw-every-frame mapper that could easily support moving chickens. On the other hand, if you don't update every frame, it's still not too difficult to save the screen, draw the chickens, and recall the image (which is what I could theoretically do...only it would cause a very very noticeable speed drop, plus I have to change/write an unaligned 12x16 mask routine, which I don't want to do just for the sake of having moving npcs.

I don't redraw the screen at every frame (that would be too slow) and can't save the entire screen either, that would be too slow and wouldn't work with the greyscale interrupt.
But now that I think again about how they work, they have a drawback that will be very annoying for 16x16 sprites: they can't be drawn if they are too close from the border of the screen. Ideally, a border of 2 pixels would be needed (but since I code bad, I put a bigger limit ).
So if there will be enemies in your game, not seeing them coming would be a huge issue

Encountering enemies is gonna be Pokémon style, I don't see any problem about that.

Erm, I don't know at all how to say that in English -.-°
When an enemy comes, you should be able to see him as soon as he has a body part on the screen (then you see that said body part).
But in TinyCraft, even when the enemy could entirely be drawn on the screen, if he is too close from the border of the screen, he is not drawn. There is the problem.

But by Pokémon style, do you mean "non-moving enemies" ? Because if they don't move, there is no problem. But I think that enemies in A:P will move, so my method will not be appliable