Support and General Use > Theming and Appearance Customization

Need Help Re: Displaying the Volume in 10% increments using Bitmap Strips

<< < (3/5) > >>

JdGordon:
yes, it entirely depends on how much accuracy you want... and we dont supply sims on this site at all...

[Saint]:

--- Quote from: JdGordon on December 03, 2009, 01:26:28 AM ---yes, it entirely depends on how much accuracy you want... and we dont supply sims on this site at all...

--- End quote ---

Ok thanks, I'll try the "13 conditional" version, play around with it, and see if I can get it to stack up visually compared to the "100+ conditional" version...I just don't want to have any (visualy percievable at least) sudden jumps in the speed of My Volume Slide Bar when scrolling through the volume.

The purpose of Me opening this thread was in order to determine whether or not there was a more effecient way to do so, as like I'd said I needed to clean up (or shorten rather) My code as much as possible due to the problems I am experiencing Re:

Maximum Tokens exceeded (1023)

And I appologise, I meant the simulator that is referenced as "trusted" by rockbox.org...

http://rasher.dk/rockbox/simulator-3.3/

I get the "Max Token Error" on the iPod Nano 1st/2nd Gen version of that Simulator, using every current build I have tried on it with My WPS including rb3.4 and the "daily builds"

I don't personally believe it's the Simulator that's at fault, as in, I don't believe the Error to be a false-positive simply for the fact that the problems I experience in the WPS on the simulator, I experience on any/all of the 2 iPod 1st and 2nd Gen's I have...(4 in total)
I have even tried to deliberately bloat the code of cabbiev2 to reproduce the error in the Simulator with success, if the max token limit is hit...random aspects of the WPS code just plain stop working.
Despit the code itself being sound and free of syntax or conditional errors....

It's got Me pretty annoyed that I've "hit a wall" persay as to the limits of what I can do personally with this WPS, but I can live with it, it should be finished relatively soon barring any huge setbacks (fingers crossed)

If a workaround could be found for that, or a solution rather, I'd be capable of building WAY cooler WPS's in future bacause as I said, this error has forced Me to cut back the visuals on My current project dramatically :'(


Sincerely,
[St.]

Llorean:
You can't try different builds on a simulator - the simulator binary is the build. You don't install builds to it. This is why it doesn't require you to download a build, and this is why it always reports the same version number until you download a new simulator.

The current Rockbox revision is in the approximate range of r23820 or so right now and is reported on the front page of the site, over a thousand revisions later than r22799.

While this may still be a problem, you should always try to make sure you're reporting with actually current builds to speed things along - the current problem may be completely unrelated to the token limit (for example, there are simply limits on RAM available to the WPS that you may have hit).

[Saint]:
What I should of said is that I use that Simulator http://rasher.dk/rockbox/simulator-3.3/ , but I always replace the .rockbox DIR with the current build from the "Daily Builds" page.

Works for Me...if it's wrong, say so, but I haven't found a better way to do it.

In saying that it was r22799 I was in error, and I'll freely admit that, but I was trying to remember a six digit number entirely off the top of My head....please excuse My fallability  :-\

Llorean:
That's a 3.3 simulator. Changing the .rockbox folder doesn't update the build for simulators, since the .exe file is the build. Changing the .rockbox folder just breaks things. You can't use a player .rockbox folder with a Rockbox simulator - they're completely different files.

Please, take the few seconds (or few minutes, or whatever) to look up the number before citing it - readers WILL assume you're telling the truth and can thus spend time trying to track down a bug or problem that no longer exists (or send you in circles down paths you've already done, or whatever) because they thought you were being accurate.

So, the simulator is entirely useless since it's not even the latest release, let alone a remotely current build. It's more than 5 months old.

Navigation

[0] Message Index

[#] Next page

[*] Previous page