695 media.show bug...

Solar2D Daily Builds and Public Releases
#1

I was going to submit a bug report, but you require a code file. That’s annoying. :wink:
If an app has this at the start:
display.setStatusBar( display.HiddenStatusBar )

… The status bar correctly hidden.

After calling:
media.show( media.SavedPhotosAlbum, onComplete )

… and selecting a photo, the StatusBar becomes unhidden and stuck in the app.

Sample code shouldn’t be need, not doing anything funky. :wink:

Tested/happens on iPhone 4S with iOS 5.0.1

No idea at what version this showed up… I’m just using Build 695.

~~Kenn [import]uid: 13859 topic_id: 18375 reply_id: 318375[/import]

#2

… Updated note:
Simply adding the code to hide the status bar to the onComplete event hides it and solves the problem…

local onComplete = function(event)
display.setStatusBar( display.HiddenStatusBar )
– blah blah code here.
return true;
end
So, it’s not the end of the world or anything. :wink: [import]uid: 13859 topic_id: 18375 reply_id: 70433[/import]

#3

Damn us and our demands for code!

Thanks for posting, will pass it along.

Peach :wink: [import]uid: 52491 topic_id: 18375 reply_id: 70498[/import]

#4

The reason we like to have code that demonstrates the problems is because the issue may only show up with your config.lua or build.settings file. It also saves us time if everything is there and ready to run.

We have seen many "bugs’ where they say just do this and that, but the bug doesn’t show up. Only when they submit a complete project do we find they are doing something elsewhere in the code that is causing the problem or when combined with a certain config.lua setting. (One bug only showed up only when [lua]anitalias=true[/lua] in config.lua.)

Thanks for reporting the problem.

-Tom

[import]uid: 7559 topic_id: 18375 reply_id: 70599[/import]

#5

@Tom … :wink:

*chuckle* I didn’t wonder “why” --> I mean I get the “why”… I said it’s annoying, and it is. :wink:

Most bugs obviously don’t occur in an empty file, so the process of requiring a file/project means the submitter has to create a project from scratch to produces even the simplest of bugs.

IMHO, by making the file a requirement, you’re losing bug reports from “lazier” people *grin*…

Do you really want the “filter” for bug reports to be the file requirement on the form that may eliminate reports from lazier people… or shouldn’t you guys really just accept ALL bug reports (making the file “strongly suggested for most reports”) and then filter them by hand… “This looks like a complicated one to reproduce, can you send back a file?”

And/or do you want ALL bug reports in the bug system for tracking purposes – namely eliminating random forum bug reports like this one. :wink: In which case, again, the file requirement is boooooo.

As always, just my humble opinions. Best wishes,
~~Kenn [import]uid: 13859 topic_id: 18375 reply_id: 70609[/import]