Quote
Definately. The thing with that is that while PSP might be more advanced as far as gaming, Wii has more memory, and after so much criticism about their lack of good online play, Nintendo decided to really focus on online capabilities.
I bet they use an existing browser too. Yup, just checked. They use Opera, whereas the PSP has a custom job. There is no way they can bring it up to the complexity of modern browsers when it's just a sideproject for their main one: the actual playing of games
Invisible War ][
Here's another one. On Firefox. I was fishing... got a fish. I clicked the reel in icon and waited for about 2 seconds (my FF was kind of laggy), saw that nothing happened and went with the mouse cursor over the white image on the button, then clicked again. This time, the button highlighted as if it was really pressed.
The "keep"/"drop" screen appeared, as in the screenshot below, but unfortunately the buttons were inoperable, since "An unknown error occurred: already_reeling".
I think that once you clicked on the reel in button, this event should somehow lock the button from subsequent clicks in the case when the browser or the Internet connection is slow and doesn't update the 'fish bit' GIF into the 'reeling in' one.
The "keep"/"drop" screen appeared, as in the screenshot below, but unfortunately the buttons were inoperable, since "An unknown error occurred: already_reeling".
I think that once you clicked on the reel in button, this event should somehow lock the button from subsequent clicks in the case when the browser or the Internet connection is slow and doesn't update the 'fish bit' GIF into the 'reeling in' one.
Edited 5 time(s). Last edited by Forger @ Wed Nov 12 1:59:23 EST 2008
Quote
Here's another one. On Firefox. I was fishing... got a fish. I clicked the reel in icon and waited for about 2 seconds (my FF was kind of laggy), saw that nothing happened and went with the mouse cursor over the white image on the button, then clicked again. This time, the button highlighted as if it was really pressed.
The "keep"/"drop" screen appeared, as in the screenshot below, but unfortunately the buttons were inoperable, since "An unknown error occurred: already_reeling".
I think that once you clicked on the reel in button, this event should somehow lock the button from subsequent clicks in the case when the browser or the Internet connection is slow and doesn't update the 'fish bit' GIF into the 'reeling in' one.
The "keep"/"drop" screen appeared, as in the screenshot below, but unfortunately the buttons were inoperable, since "An unknown error occurred: already_reeling".
I think that once you clicked on the reel in button, this event should somehow lock the button from subsequent clicks in the case when the browser or the Internet connection is slow and doesn't update the 'fish bit' GIF into the 'reeling in' one.
It does. It hides the button
Invisible War ][
Quote
It does. It hides the button
Well... apparently it hides the button in most cases, but not all.
When the page loads slowly though - that's how I caught this error, if the connection and the browser would have worked at normal params, this wouldn't have occurred - there is a chance that the reel in button will not record the event of being pressed until after it throws away that error.
That is, to say, your 'already_reeling' mutex is slightly defective
Quote
Quote
It does. It hides the button
Well... apparently it hides the button in most cases, but not all.
When the page loads slowly though - that's how I caught this error, if the connection and the browser would have worked at normal params, this wouldn't have occurred - there is a chance that the reel in button will not record the event of being pressed until after it throws away that error.
That is, to say, your 'already_reeling' mutex is slightly defective
I suspect that it's simple to fix and arises almost always as a result of a weird connection delay or misclick. I will try to lock out buttons upon receiving the click event.
Invisible War ][