02-22-2013, 07:54 PM
Quote:You haven't asked any question about JList though. Obviously people won't care about your problems if you don't take the time to explain properly.This. Be more specific so we know what to help you with.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67
02-22-2013, 07:54 PM
02-23-2013, 02:25 AM
(02-21-2013, 10:44 AM)ExtremeDude2 Wrote: [ -> ]I'm pretty sure that's because it's made by jabo...
The Android port is written in Java. :p
EDIT: Well, maybe not, I have no way to tell. HalfNES, however, is an NES emulator written in Java for sure.
02-23-2013, 02:42 AM
I was about to ask how you know this then I saw your edit XD
02-23-2013, 03:30 AM
(02-23-2013, 02:42 AM)ExtremeDude2 Wrote: [ -> ]I was about to ask how you know this then I saw your edit XD
Most Android apps are written in Java, but you can use C or C++. I'm not familiar with the Android app dev community, but I get the feeling a majority use Java. JNES isn't open-source, so unless you ask Jabo himself, or try to disassemble the program, it isn't immediately obvious what he programmed the Android port in.
02-23-2013, 11:37 AM
Basically I had no clue at all about JLists, and there was a bit more information in the original version of the question. Anyway, I've got hold of the java GUI 'cheat sheet' my teacher made, which, somehow, is much simpler than anything else I can find.
03-11-2013, 05:44 PM
Hi all.
It's been long since last time I was here, and just saw this thread and I hoped perhaps I could get some advise...
I'm trying to implement exponentiation of a number in assembler language (for the 8051 processor in this case). I'm trying by using the MUL instruction, which does the multiplication of 2 numbers stored in registers A (accumulator) and B, and puts the lower 8 bits in A and the upper ones in B. So the exercise is, I have initially numbers in A and B, and we want the operation A^B leaving lower 8 bits in A and upper ones in B.
I'm trying first with a particular case: 3^10. I already have part of the overall idea, I'm making a loop that multiplies A itself B number of times, making 8 bit multiplications (obviously storing previous results in other R registers). When I reach the 6th power the upper 8 bits (register B) begins to be used. I did the following binary multiplications in calculator apart in 2 ways: taking all the 8+ bits and taking only the lower 8 bits. Compared and realized that in both cases the lower 8 bits remain the same, only the upper 8 bits changing.
So the idea of doing 8-bit multiplications seems good. My problems are, I just have no clue of how to gradually do the arrangements on the upper 8 bits, nor I know how to stop the program if the result exceeds the 16 total bits (according to MUL's instruction manual, the overflow flag sets when the product exceeds 255, not 65535, where it's actually needed!).
Can you help me by chance?
Thank you beforehand.
It's been long since last time I was here, and just saw this thread and I hoped perhaps I could get some advise...
I'm trying to implement exponentiation of a number in assembler language (for the 8051 processor in this case). I'm trying by using the MUL instruction, which does the multiplication of 2 numbers stored in registers A (accumulator) and B, and puts the lower 8 bits in A and the upper ones in B. So the exercise is, I have initially numbers in A and B, and we want the operation A^B leaving lower 8 bits in A and upper ones in B.
I'm trying first with a particular case: 3^10. I already have part of the overall idea, I'm making a loop that multiplies A itself B number of times, making 8 bit multiplications (obviously storing previous results in other R registers). When I reach the 6th power the upper 8 bits (register B) begins to be used. I did the following binary multiplications in calculator apart in 2 ways: taking all the 8+ bits and taking only the lower 8 bits. Compared and realized that in both cases the lower 8 bits remain the same, only the upper 8 bits changing.
So the idea of doing 8-bit multiplications seems good. My problems are, I just have no clue of how to gradually do the arrangements on the upper 8 bits, nor I know how to stop the program if the result exceeds the 16 total bits (according to MUL's instruction manual, the overflow flag sets when the product exceeds 255, not 65535, where it's actually needed!).
Can you help me by chance?
Thank you beforehand.
03-17-2013, 04:25 AM
8 bits * 8 bits can never overflow 16 bits: the largest value contained on 8 bits is 255 and 255 * 255 = 65025 which is less than 65535.
03-26-2013, 02:42 AM
03-26-2013, 03:05 AM
>all those else if statements
![[Image: HeresyStamp.png]](http://media.moddb.com/cache/images/groups/1/3/2055/thumb_620x2000/HeresyStamp.png)
03-26-2013, 03:36 AM
Damn NaturalViolence. And here I thought you were analyzing and writing up a detailed analysis of yours of what he did wrong and how he could do it better.
This piece of code for example, makes no sense.
First, you have declared playing as an unsigned short. Better practice is it to make it a bool.
Then you have the function from above which accepts an integer as a parameter which you then check locally if it's true or false.
If you do it this way, you could render the playing variable above useless, as you might as well pass a 0 or 1 to it.
Don't forget about the different datatypes. You are currently passing a short to the function.
You're also checking your parameter redundantly. If you're making checks, you only have to check if a variable is true, otherwise return false.
For better practice, which you'll definitely want when you're working with objects and classes, is to have getters and setters.
Getters to receive the value of the variable and setters to set a value to it.
So something like this:
Also, if you declare variables, you should declare them individually and name the properly. It makes it easier to follow.
Now master this and enter the beauty of Object Oriented Programming.
This piece of code for example, makes no sense.
Code:
unsigned short playing = 1; //removed other variables for readability
bool game_playing(int playing)
{
if (playing)
return true;
else if (!playing)
return false;
return true;
}First, you have declared playing as an unsigned short. Better practice is it to make it a bool.
Then you have the function from above which accepts an integer as a parameter which you then check locally if it's true or false.
If you do it this way, you could render the playing variable above useless, as you might as well pass a 0 or 1 to it.
Don't forget about the different datatypes. You are currently passing a short to the function.
You're also checking your parameter redundantly. If you're making checks, you only have to check if a variable is true, otherwise return false.
For better practice, which you'll definitely want when you're working with objects and classes, is to have getters and setters.
Getters to receive the value of the variable and setters to set a value to it.
So something like this:
Code:
bool isPlaying = true;
bool isPlaying() {
if (isPlaying) //if isPlaying = true
return true; //return true and exit function
return false; //this statement only gets reached when isPlaying is false
}
//note that the piece below is for classes
void setPlaying(bool isPlaying) {
this->isPlaying = isPlaying;
}Also, if you declare variables, you should declare them individually and name the properly. It makes it easier to follow.
Now master this and enter the beauty of Object Oriented Programming.