try discovering why running a procedure on a full list produces different results to running a procedure on half the list and then finishing the list and running the procedure again, when the only thing the procedure does is delete duplicates from the list!
awww poor you! The API and Java tutorial are your friends!
can't be arsed to read the api... too confusing. Arthur Norman's specification for this thing isn't helping much either. I guess I'll have to leave the difficult part till after the term starts.
the API is the bible of Java....it makes everything so easy to understand. And for the REALLY basic things, just use the Java Tutorial. Like understanding public and private and how they limit access etc!
try discovering why running a procedure on a full list produces different results to running a procedure on half the list and then finishing the list and running the procedure again, when the only thing the procedure does is delete duplicates from the list!
Okay, just to check:
1. Have half the list. 2. Run procedure on half the list. 3. Populate second half of list. 4. Run procedure on entire list. 5. Result differs?
Seems like the problem is most likely to be that you need to be definitely running it the second time on the entire list. Is there any particular reason why you'd want it to run the duplicate removal multiple times, is space really an issue?
the API is the bible of Java....it makes everything so easy to understand. And for the REALLY basic things, just use the Java Tutorial. Like understanding public and private and how they limit access etc!
That's not the part I'm worrying about... it's the "not understanding part of the specification" bit I'm worrying about. I can do quite a bit of this thing, construct necessary classes, doing about 25% of the gui... There's the JPanel's paintComponent, which I've no idea about. There's something about a custom class called Document and a method used to associate a JPanel (or its subclass) with an instance of Document which I also have no idea about. other than that. It's cool.
Actually... nothing for me is "cool" with this piece of work.
1. Have half the list. 2. Run procedure on half the list. 3. Populate second half of list. 4. Run procedure on entire list. 5. Result differs?
Seems like the problem is most likely to be that you need to be definitely running it the second time on the entire list. Is there any particular reason why you'd want it to run the duplicate removal multiple times, is space really an issue?
Incidentally, how are you removing duplicates?
A.
i found the problem in the end. When a duplicate was removed from the list, the indices were automatically decreased by 1 for all following items. However the procedure was using a for loop to go through the items, and so this meant it was skipping an item each time there was a removal of a duplicate. So I just added an "i--" into the code.
I should either go to bed, or drink large quantities of hot coffee... Not sleeping is not good me... 12 hours to go till dark . I need to get rid of my beard.
you haven't been to sleep yet? oh dear. I've been to sleep and got up and now I'm in work.
I got up at 4pm yesterday... I'm taking this opportunity to adjust my biological clock. I was hoping to get some work done today. But I'm afraid I will only be fit enough to produce garbage for the garbage collector today ...