Bug: Sansa e200V2 simulator ALT+F4 fails

[chrisjj]

Steps:

1 Launch Sansa e200V2 simulator (here, from http://rasher.dk/rockbox/simulator/)
2 Press ALT+F4

Expected: exit
Observed: no effect

OS: Win XP SP2
RB: Version r24777-100-219

[Llorean]

1) You clearly know the forums aren't the right place for bug reports (or should, since you read the guidelines and reported an error in them).

2) Is there any documentation that says Alt+F4 is supposed to do that in the simulator? There are many, many windows programs that don't treat Alt+F4 as an exit combination. Unless there's something that says it's meant to do this, it shouldn't be "expected" behavior.

[saratoga]

I don't think this is a bug, and honestly unless you've got a way to change the behavior its not worth anyone's time.

[chrisjj]

> the forums aren't the right place for bug reports

Oops, sorry - reposted at http://www.rockbox.org/tracker/task/11225.

> 2) Is there any documentation that says Alt+F4 is supposed to do that in the simulator?

The title bar menu.

> Unless there's something that says it's meant to do this, it shouldn't be "expected" behavior.

Agreed 100%.

[Llorean]

The bug is actually that the title bar menu says that, I believe, then.

[chrisjj]

The bug is actually that the title bar menu says that, I believe, then.

I'll go with your:

Unless there's something that says it's meant to do this, it shouldn't be "expected" behavior.

[Llorean]

Yes, in the code or manual.

Basically, a bug is when something does something it's not supposed to do. In this case, it's not supposed to tell you about a button combination that doesn't exist.

[chrisjj]

> In this case, it's not supposed to tell you about a button combination that doesn't exist.

OOI, how can you tell ?

[Llorean]

I have no idea what "OOI" means. As the guidelines also said, please try not to use abbreviations except in places where they're technical terms relating to the project.

I'll admit there's no good way to tell that Alt+F4 isn't supposed to do anything for the casual user - that's what makes it a problem.

[chrisjj]

> I have no idea what "OOI" means.

"Out of Interest"

> As the guidelines also said, please try not to use abbreviations except in places where
> they're technical terms relating to the project.

Oops, sorry.

> I'll admit there's no good way to tell that Alt+F4 isn't supposed to do anything for the casual user

What was the way that was good enough for you?

[Llorean]

Well the way that was good enough for me is that a developer posted in the thread that he doesn't think this is a bug.

And that it's a cross platform app generally intended to perform the same on other OSes that don't follow the "Alt+F4 = close window" paradigm.

And that, generally, it's not intended to respond to any keypresses beyond those that represent inputs on the player, because it's a simulator.

Another option would be to check the source code to find out what it's intended to do, though I didn't personally go that far.

[chrisjj]

> Well the way that was good enough for me is that a developer posted in the thread that he doesn't think this is a bug.

Well, we've agreed it must be a bug, in action or UI.

> And that it's a cross platform app generally intended to perform the same on other OSes
> that don't follow the "Alt+F4 = close window" paradigm.

I guess another OS would have its key for close.

> And that, generally, it's not intended to respond to any keypresses beyond those that represent
> inputs on the player, because it's a simulator.

Windows apps generally respond to standard Windows app keys because they are Windows apps !

> Another option would be to check the source code to find out what it's intended to do

 

[Llorean]

I don't see what's funny. It's an honest answer - this is open source.

And many, many windows apps don't close on Alt+F4 (see for example, >90% of videogames ever made as a starting point). It's something that many applications do *when it makes sense* but plenty others ignore it because it's not part of the functionality.

[chrisjj]

> It's something that many applications do *when it makes sense*

Which is why it seems to me it would be good for this one to do it.

[Llorean]

But "I think it should do it" doesn't make the lack of it a bug.

Feel free to submit a patch for it though.

But the simulator is meant to simulate the normal operation of a Rockbox device - you should power it off by pressing whatever button or combo would power off the device. It is *not* a full application meant to work like a normal native windows application.