Homebrew Homebrew Development

[AlbertoSONIC]

Python eh?

http://learnpythonthehardway.org/

Free version of the e-book if you prefer:

http://learnpythonthehardway.org/book/

Enjoy, it's also a recommended book by the r/programming subreddit, so I'm assuming it's pretty good.
I haven't read it myself, but I plan to read it to use as material to help teach my younger cousin programming in the future.

Anyway, enjoy, and also, that same guy has a book on C as well, might want to check it out.

Thank you, really! You guys at GBATemp are awesome!

 

[AlbertoSONIC]

I finally got it to work!
https://github.com/AlbertoSONIC/3DSBinaryConverter

But i'm having some graphical issue...

How can i fix it? I really need help!

EDIT1: Plus, i need help for int --> char* conversion... Because it seems to crash once it reaches the result printing point.

EDIT2: Is there some way to increase font size?

 

[Relys]

I finally got it to work!
https://github.com/AlbertoSONIC/3DSBinaryConverter

But i'm having some graphical issue...


How can i fix it? I really need help!

Plus, i need help for int --> char* conversion...

It's probably because you're only writing to 1/2 framebuffers (and you're using a hardcoded addr as opposed to swaping with the gfx lib).

For int-->char just search for "itoa in c" function and port it over.

 

[AlbertoSONIC]

It's probably because you're only writing to 1/2 framebuffers (and you're using a hardcoded addr as opposed to swaping with the gfx lib).

For int-->char just search for "itoa in c" function and port it over.

Please explain framebuffer thing...

 

[Reisyukaku]

Please explain framebuffer thing...

Basically theres like 3 areas in RAM that hold the screen data.. bottom screen, top screen left eye, and top screen right eye.. you might only be writing to one of the top screen buffers and not the other.. theres 2 because the 3D effect uses it

 

[AlbertoSONIC]

Basically theres like 3 areas in RAM that hold the screen data.. bottom screen, top screen left eye, and top screen right eye.. you might only be writing to one of the top screen buffers and not the other.. theres 2 because the 3D effect uses it

But i'm writing to the bottom screen...

 

[Reisyukaku]

But i'm writing to the bottom screen...

oh yea, thats right.. idk lol ¯\_(ツ)_/¯

 

[YourNerdyJoe]

But i'm writing to the bottom screen...

All the screens have both a frontbuffer and backbuffer (sometimes I've seen it refered to as framebuffer 0/1).
What you do is write to the backbuffer then flip (or swap) the buffers to see it rendered to the screen.
If one of the buffers is blank then the screen flashes all weird.

 

[AlbertoSONIC]

All the screens have both a frontbuffer and backbuffer (sometimes I've seen it refered to as framebuffer 0/1).
What you do is write to the backbuffer then flip (or swap) the buffers to see it rendered to the screen.
If one of the buffers is blank then the screen flashes all weird.

I'll see tomorrow... Good night guys!

 

[Relys]

I'll see tomorrow... Good night guys!

Had to re-write pretty much everything. Here it is.

https://github.com/Relys/3DSBinaryConverter

 

[AlbertoSONIC]

Had to re-write pretty much everything. Here it is.

https://github.com/Relys/3DSBinaryConverter

So, basically i need to render everything twice? If so, then today i'll fix my code and then i'll start cleaning it up...

 

[AlbertoSONIC]

Guys i finally fixed almost everything (except a little framebuffer bug... )! I can only thank Relys for his code! I didn't copied it.. But it helped me a lot!


P.S. If someone could help me with that framebuffer bug i would appreciate his help...

As you can see, the inserted binary number isn't fully clear.

Also, i removed the github repo because it didn't want to sync. Now you can find all source code here: www.github.com/AlbertoSONIC/3DS_Binary_Decimal_Converter

I think that now this is a good code. Let me know your feedback!

Again, it wouldn't work without Relys 's help!

 

[YoshiInAVoid]

Guys i finally fixed almost everything (except a little framebuffer bug... )! I can only thank Relys for his code! I didn't copied it.. But it helped me a lot!


P.S. If someone could help me with that framebuffer bug i would appreciate his help...

As you can see, the inserted binary number isn't fully clear.

Also, i removed the github repo because it didn't want to sync. Now you can find all source code here: www.github.com/AlbertoSONIC/3DS_Binary_Decimal_Converter

I think that now this is a good code. Let me know your feedback!

Good program. Source looks well written too. I have a minor suggestion for this line though:

converted += val[7] * 1 + val[6] * 2 + val[5] * 4 + val[4] * 8 + val[3] * 16 + val[2] * 32 + val[1] * 64 + val[0] * 128;

You should learn how to use the << operator.

n << 1 = n * 2
n << 2 = n * 4
n << 3 = n * 8
n << 4 = n * 16
n << 5 = n * 32
n << 6 = n * 64
n << 7 = n * 128
n << 8 = n * 256
etc...

Although the result is the same as multiplication, the << operator is slightly faster in most cases, and it just looks more correct when dealing with bits since that is it's intended purpose.

 

[AlbertoSONIC]

Good program. Source looks well written too. I have a minor suggestion for this line though:

converted += val[7] * 1 + val[6] * 2 + val[5] * 4 + val[4] * 8 + val[3] * 16 + val[2] * 32 + val[1] * 64 + val[0] * 128;

You should learn how to use the << operator.

n << 1 = n * 2
n << 2 = n * 4
n << 3 = n * 8
n << 4 = n * 16
n << 5 = n * 32
n << 6 = n * 64
n << 7 = n * 128
n << 8 = n * 256
etc...

Although the result is the same as multiplication, the << operator is slightly faster in most cases, and it just looks more correct when dealing with bits since that is it's intended purpose.

So i have to replace every * with <<?

 

[YoshiInAVoid]

So i have to replace every * with <<?

You don't have to, it is just better practice to use bitwise operators when performing bit operations rather than multiplication.

If you have "n * 256" you can replace it with "n << 8" for example.

 

[AlbertoSONIC]

You don't have to, it is just better practice to use bitwise operators when performing bit operations rather than multiplication.

If you have "n * 256" you can replace it with "n << 8" for example.

If << is better then I definitely HAVE TO use it!

 

[YoshiInAVoid]

If << is better then I definitely HAVE TO use it!

You should read more into it, I didn't really explain it very well. http://en.wikipedia.org/wiki/Bitwise_operations_in_C#Left_shift_.3C.3C

 

[AlbertoSONIC]

You should read more into it, I didn't really explain it very well. http://en.wikipedia.org/wiki/Bitwise_operations_in_C#Left_shift_.3C.3C

It seems that it doesn't work as i want, according to wikipedia...
Can i do n<<2+n<<3+n<<4 with it?

 

[YoshiInAVoid]

It seems that it doesn't work as i want, according to wikipedia...
Can i do n<<2+n<<3+n<<4 with it?

You should use brackets:

(n<<2)+(n<<3)+(n<<4)

 

[AlbertoSONIC]

You should use brackets:

(n<<2)+(n<<3)+(n<<4)

Right.
Is n<<3 the same as n*8?