Support and General Use > User Interface and Voice
Bug: Sansa e200V2 simulator ALT+F4 fails
AlexP:
--- Quote from: chrisjj on May 04, 2010, 06:31:50 PM ---
--- Quote from: Llorean on May 04, 2010, 06:06:49 PM --- As a clue, check the manual before asking questions.
--- End quote ---
I checked the only manual I've found for the simulator, and it didn't answer. Perhaps because, as you say, it is only in the wiki (http://www.rockbox.org/wiki/UiSimulator), hence unofficial.
--- End quote ---
The sim for the most part works the same as Rockbox on a device, and so the manual for the most part applies to both.
--- Quote from: chrisjj on May 04, 2010, 06:31:50 PM ---
--- Quote from: Llorean on May 04, 2010, 06:06:49 PM ---if you're filing a bug report it should be against the most recent version possible.
--- End quote ---
I think you're mistaken. There is no such project requirement - see http://www.rockbox.org/wiki/FlySprayHowto .
And I am glad there is not - such a requirement would unduly hamper reporting.
--- End quote ---
There should be such a requirement there, it is commonly asked for - it wastes a huge amount of time investigating bug reports for bugs that have already been fixed.
Llorean:
--- Quote from: chrisjj on May 04, 2010, 06:31:50 PM ---I was expecting a version number specific to the simulator, but if it is the same as Rockbox for device, fine.
--- End quote ---
It is. The simulators are build from the exact same source. A simulator for a target will only behave the same as the target if they have the exact same revision number, which tells they were built from the same revision of the code.
--- Quote from: chrisjj on May 04, 2010, 06:31:50 PM ---
--- Quote from: Llorean on May 04, 2010, 06:06:49 PM --- As a clue, check the manual before asking questions.
--- End quote ---
I checked the only manual I've found for the simulator, and it didn't answer. Perhaps because, as you say, it is only in the wiki (http://www.rockbox.org/wiki/UiSimulator), hence unofficial.
--- End quote ---
There is no separate manual for the simulator. Outside of the controls, everything within the simulator for a specific target should work as Rockbox does on that player, thus the player manual is what should be referenced for the simulator in almost all cases.
--- Quote from: chrisjj on May 04, 2010, 06:31:50 PM ---
--- Quote from: Llorean on May 04, 2010, 06:06:49 PM ---if you're filing a bug report it should be against the most recent version possible.
--- End quote ---
I think you're mistaken. There is no such project requirement - see http://www.rockbox.org/wiki/FlySprayHowto .
And I am glad there is not - such a requirement would unduly hamper reporting.
--- End quote ---
I note you're once more referencing the wiki. And suggesting I said it was required - "should be" is different from "must be" hence the difference in meaning of the words. Whether or not it's a requirement though, it makes sense that a several month old version that is 1000 revisions behind current SVN is out of date and missing many things.
It's not a requirement, but it's heavily suggested that reports be made against the most current revision possible (you'll notice that word choice was important too). This means, for example, that we expect you at least to make an attempt to not have reported against heavily outdated code. Reporting against completely random versions just fills the tracker with reports on things already fixed (because searching the tracker isn't enough - there isn't always a bug report for something) or on features that simply don't work the same way any more.
If you don't feel up to compiling the latest code, you can report bugs against a release version. But since the simulator is for development (either development of the manual, development of Rockbox, or development of WPSes) it's not unreasonable to expect people working with it to be using the most recent build (as there is no other truly relevant build of the sim than the most recent one for any of these purposes).
chrisjj:
--- Quote ---It's not a requirement
--- End quote ---
Thanks for the clarification.
--- Quote --- but it's heavily suggested that reports be made against the most current revision possible
--- End quote ---
If that's true, don't you think it very odd there is not remotely any such mention in the FlySprayHowto ??
--- Quote ---Reporting against completely random versions just fills the tracker with reports on things already fixed ).
--- End quote ---
Agreed. That's why I didn't.
--- Quote ---If you don't feel up to compiling the latest code, you can report bugs against a release version.
--- End quote ---
Great. Now where does one find that version's simulator built for Windows? Thanks.
Llorean:
--- Quote from: chrisjj on May 04, 2010, 06:31:50 PM ---If that's true, don't you think it very ofdd there is not remotely any such mention in the FlySprayHowto ??
--- End quote ---
It's a wiki page. Possibly some irate user who disagrees with it removed it? Possibly nobody thought to add it because "bug reports shouldn't be against outdated versions" seems the most blatantly obvious thing that nobody thought it needed to be explicit. Especially considering the version dropdown in Flyspray only allows you specific choices, and it's a clue when your version isn't one of those choices that it's the wrong one (something you ignored and just lied about there).
--- Quote from: chrisjj on May 04, 2010, 06:52:03 PM ---Great. Now where does one find that version's simulator built for Windows? Thanks.
--- End quote ---
One compiles it, as I said.
AlexP:
--- Quote from: chrisjj on May 04, 2010, 06:52:03 PM ---
--- Quote --- but it's heavily suggested that reports be made against the most current revision possible
--- End quote ---
If that's true, don't you think it very ofdd there is not remotely any such mention in the FlySprayHowto ??
--- End quote ---
It is mentioned now.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version