Rockbox Ports are now being developed for various digital audio players!
Quote from: Llorean on May 04, 2010, 06:06:49 PM As a clue, check the manual before asking questions.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.
As a clue, check the manual before asking questions.
Quote from: Llorean on May 04, 2010, 06:06:49 PMif you're filing a bug report it should be against the most recent version possible.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.
if you're filing a bug report it should be against the most recent version possible.
I was expecting a version number specific to the simulator, but if it is the same as Rockbox for device, fine.
It's not a requirement
but it's heavily suggested that reports be made against the most current revision possible
Reporting against completely random versions just fills the tracker with reports on things already fixed ).
If you don't feel up to compiling the latest code, you can report bugs against a release version.
If that's true, don't you think it very ofdd there is not remotely any such mention in the FlySprayHowto ??
Great. Now where does one find that version's simulator built for Windows? Thanks.
Quote but it's heavily suggested that reports be made against the most current revision possibleIf that's true, don't you think it very ofdd there is not remotely any such mention in the FlySprayHowto ??
Basically, bug reports should be against one of two things - a binary we release or currently provide (such as bootloaders or rbutils or the most recent actual Rockbox releases), or the current state of SVN.
At the moment, we don't provide simulator binaries
That's basically my point - if you make a bug report against anything but that, it's almost certainly going to get a response "can you reproduce it with the current code"
There's still a question as to whether the current state will even be considered a bug - at the moment it certainly does what the programmers expected it to do, which would qualify relatively clearly as "not a bug"
and since there's no documentation for or released sim
Again, the WIKI is not official documentation.
Someone other than Rockbox providing builds does not matter.
The manual documents programmer intent.
you should ask a developer of that part of it "is this how it's supposed to work" before deciding that your assumption about how it's supposed to work is right, and file a bug.
Quote from: Llorean on May 05, 2010, 04:27:33 PMAt the moment, we don't provide simulator binariesYou don't. Others do.
Quote from: Llorean on May 05, 2010, 07:35:21 PMThe manual documents programmer intent.Except where it doesn't - such as here.
However, as we have no control about such binaries why should we even want to support those?
I'm not sure if you're still discussing this stupid Alt-F4 thing but if you do please point me to where the manual tells that Alt-F4 quits the simulator.
Quote from: bluebrother on May 06, 2010, 02:10:01 PMHowever, as we have no control about such binaries why should we even want to support those?I don't see anyone suggesting you'd want to support binaries. Or for that matter you'd want to support the simulator at all. But since Rockbox Flyspray has a category for Simulator, I presume it is because the project wants to hear about simulator bugs that are found. If not, please do tell me what you think it is for.
Quote from: bluebrother on May 06, 2010, 02:10:01 PMI'm not sure if you're still discussing this stupid Alt-F4 thing but if you do please point me to where the manual tells that Alt-F4 quits the simulator. Nowhere I can see. However, given that the manual is unofficial, what do you care?
If there is a developer tool does it make sense to track issues with that tool even if it's not an end user tool or not?
The Rockbox manual is the official manual, and officially maintained and supported. Who said that the manual is unofficial?
The Simulator manual (such as exists) is in the Wiki, and it has been said here that the wiki is unofficial.
Page created in 0.11 seconds with 21 queries.