{"action":"created","issue":{"url":"https://api.github.com/repos/ftlabs/screens/issues/56","labels_url":"https://api.github.com/repos/ftlabs/screens/issues/56/labels{/name}","comments_url":"https://api.github.com/repos/ftlabs/screens/issues/56/comments","events_url":"https://api.github.com/repos/ftlabs/screens/issues/56/events","html_url":"https://github.com/ftlabs/screens/issues/56","id":122235200,"number":56,"title":"Some way of having a screen identify itself","user":{"login":"seanmtracey","id":913687,"avatar_url":"https://avatars.githubusercontent.com/u/913687?v=3","gravatar_id":"","url":"https://api.github.com/users/seanmtracey","html_url":"https://github.com/seanmtracey","followers_url":"https://api.github.com/users/seanmtracey/followers","following_url":"https://api.github.com/users/seanmtracey/following{/other_user}","gists_url":"https://api.github.com/users/seanmtracey/gists{/gist_id}","starred_url":"https://api.github.com/users/seanmtracey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/seanmtracey/subscriptions","organizations_url":"https://api.github.com/users/seanmtracey/orgs","repos_url":"https://api.github.com/users/seanmtracey/repos","events_url":"https://api.github.com/users/seanmtracey/events{/privacy}","received_events_url":"https://api.github.com/users/seanmtracey/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ftlabs/screens/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-12-15T10:00:48Z","updated_at":"2015-12-15T15:00:42Z","closed_at":null,"body":"When looking at a screen that's already been assigned content, it's very hard to deduce what it's ID is without either popping the content it already has from the stack or adding something new. This issue is lessened by having nice semantically named screens, but in the case where the admin panel is just a sea of screen IDs, it would be nice to have a way to make the screen identify themselves without affecting the content stack it has.\r\n\r\nPerhaps if we added a 'identify' option to the dropdown list in the footer? Maybe it could make the selected screen flash for a few ms (like when you make an error in Terminal and your volume is down way low) or it displays it's ID in the corner for a few seconds over the existing content."},"comment":{"url":"https://api.github.com/repos/ftlabs/screens/issues/comments/164789652","html_url":"https://github.com/ftlabs/screens/issues/56#issuecomment-164789652","issue_url":"https://api.github.com/repos/ftlabs/screens/issues/56","id":164789652,"user":{"login":"seanmtracey","id":913687,"avatar_url":"https://avatars.githubusercontent.com/u/913687?v=3","gravatar_id":"","url":"https://api.github.com/users/seanmtracey","html_url":"https://github.com/seanmtracey","followers_url":"https://api.github.com/users/seanmtracey/followers","following_url":"https://api.github.com/users/seanmtracey/following{/other_user}","gists_url":"https://api.github.com/users/seanmtracey/gists{/gist_id}","starred_url":"https://api.github.com/users/seanmtracey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/seanmtracey/subscriptions","organizations_url":"https://api.github.com/users/seanmtracey/orgs","repos_url":"https://api.github.com/users/seanmtracey/repos","events_url":"https://api.github.com/users/seanmtracey/events{/privacy}","received_events_url":"https://api.github.com/users/seanmtracey/received_events","type":"User","site_admin":false},"created_at":"2015-12-15T15:00:42Z","updated_at":"2015-12-15T15:00:42Z","body":"No, you've got the scenario spot on. The physical web would be a great way to resolve, or narrow this problem. But with our current setup, we're still stuck with a trial and error system, but at least we could make figuring out the screen ID a less intrusive process. "}}