Bug: Sansa e200V2 simulator ALT+F4 fails

[chrisjj]

> you should power it off by pressing whatever button or combo would power off the device.

That would be Long Power. It doesn't work.

> It is *not* a full application meant to work like a normal native windows application.

Well, I can't see the advantage of this one keypress not working and hence requiring the mouse, esp. since all other program functions are operated by keypresses and none by mouse.

[Llorean]

So the real problem is that you can't quit it using the keypresses that would power down the player?

[chrisjj]

So the real problem is that you can't quit it using the keypresses that would power down the player?

No. I'd say there's a separate problem in the failure of Long Power to power down the simulated device. I would not expect it to close the window, esp. since that would prevent Powering the device back again e.g. to test fixed .CFG.

[Llorean]

You can just re-launch the app to "power it back on again."

[chrisjj]

OK, but shouldn't Long Power work?

[Llorean]

So the real problem is that you can't quit it using the keypresses that would power down the player?

[chrisjj]

Sorry, I've lost you.

The device docs says Long Power powers down the player.

In the sim, it doesn't. All other device buttons work - just not this one.

[Llorean]

Yes. As I said, it sounds like the fact that this doesn't work is a problem. And then, later, you asked me if it should work.

Obviously if it's a problem that it doesn't work, that means it should work. I quoted my mentioning of the fact that its not working was a problem in the hopes that you'd realized I'd already acknowledged the point.

[karashata]

So the real problem is that you can't quit it using the keypresses that would power down the player?

No. I'd say there's a separate problem in the failure of Long Power to power down the simulated device. I would not expect it to close the window, esp. since that would prevent Powering the device back again e.g. to test fixed .CFG.

Okay, since the simulator is a simulator it is kind of limited in exactly what it can and can't do by nature. It can't give you any idea how the hardware should perform since it's not running on that hardware, and is not an emulator of that hardware. It is a simulator of the rockbox interface for that particular device and is intended to showcase how the interface works.

In reality its best use (as far as I'm concerned anyway) is for making themes for the device in question, and any other use really would be any bug testing that's not dependent directly on the hardware. As such, having the interface act exactly like the hardware isn't entirely necessary as long as the simulator has controls appropriate to the available buttons on the hardware in order to control the interface (ie. navigation, volume control, etc.).

[chrisjj]

Reported as a bug:

FS#11238 - Sansa e200 v2 simulator - long power press fails to power-off device
http://www.rockbox.org/tracker/task/11238

[Llorean]

Just as a note for that bug report, the "reported version" shouldn't be 3.4 (as 3.4 only refers to the actual 3.4 release, not any later builds) and your version number is also written wrong (they don't include two dashes).

It's also a relatively out of date version, and we ask that bug reports be against the most recent version of the code available. The simulator is a development tool, and you should generally be building your own rather than depending on a random person's outdated hosted versions.

[chrisjj]

Thanks for the feedback.

Just as a note for that bug report, the "reported version" shouldn't be 3.4 (as 3.4 only refers to the actual 3.4 release, not any later builds)

OK - noted.

and your version number is also written wrong (they don't include two dashes).

Where on the simulator distribution should I look for the correct version number? I find none in the regular. exe properties.

It's also a relatively out of date version, and we ask that bug reports be against the most recent version of the code available.

That was the latest version available to me, since I don't have build facilities.

The simulator is a development tool

I was using it for "Test other devices for working on the Manual." as per http://rasher.dk/rockbox/simulator/

and you should generally be building your own rather than depending on a random person's outdated hosted versions.

Are the "unofficial (but trusted) pre-compiled Windows versions of the simulators" (http://www.rockbox.org/wiki/UiSimulator#Download) found here: http://rasher.dk/rockbox/simulator/ acceptable?

[Llorean]

Where on the simulator distribution should I look for the correct version number? I find none in the regular. exe properties.

The same place you find version numbers in Rockbox. As a clue, check the manual before asking questions.

Are the "unofficial (but trusted) pre-compiled Windows versions of the simulators" (http://www.rockbox.org/wiki/UiSimulator#Download) found here: http://rasher.dk/rockbox/simulator/ acceptable?

If they were, I wouldn't have been saying "you should build your own" but rather "you should build your own, or use the ones from rasher.dk"

They're often out of date. When they're out of date, they can be missing whole features, or have controls completely different than current Rockbox. While I expect your problem still exists in them, an assumption that it does should never be made - if you're filing a bug report it should be against the most recent version possible.

The tools necessary to compile Rockbox and its simulators are free and available for all the major OSes, and the instructions are relatively simple.

[chrisjj]

The same place you find version numbers in Rockbox.

I was expecting a version number specific to the simulator, but if it is the same as Rockbox for device, fine.

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.

if 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.

[gevaerts]

if 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 .

You have pointed out yourself that the wiki can be incomplete and outdated.