{"action":"created","issue":{"url":"https://api.github.com/repos/oe-alliance/enigma2-plugins/issues/86","repository_url":"https://api.github.com/repos/oe-alliance/enigma2-plugins","labels_url":"https://api.github.com/repos/oe-alliance/enigma2-plugins/issues/86/labels{/name}","comments_url":"https://api.github.com/repos/oe-alliance/enigma2-plugins/issues/86/comments","events_url":"https://api.github.com/repos/oe-alliance/enigma2-plugins/issues/86/events","html_url":"https://github.com/oe-alliance/enigma2-plugins/issues/86","id":164219479,"number":86,"title":"Optional search restriction in epgsearch","user":{"login":"prl001","id":7552983,"avatar_url":"https://avatars.githubusercontent.com/u/7552983?v=3","gravatar_id":"","url":"https://api.github.com/users/prl001","html_url":"https://github.com/prl001","followers_url":"https://api.github.com/users/prl001/followers","following_url":"https://api.github.com/users/prl001/following{/other_user}","gists_url":"https://api.github.com/users/prl001/gists{/gist_id}","starred_url":"https://api.github.com/users/prl001/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/prl001/subscriptions","organizations_url":"https://api.github.com/users/prl001/orgs","repos_url":"https://api.github.com/users/prl001/repos","events_url":"https://api.github.com/users/prl001/events{/privacy}","received_events_url":"https://api.github.com/users/prl001/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":54,"created_at":"2016-07-07T03:00:18Z","updated_at":"2016-07-11T13:20:03Z","closed_at":null,"body":"There have been a number of requests on the Beyonwiz forum to allow epgsearch to restrict its search to the current bouquet, especially for users who normally have \"Enable multiple bouquets\" disabled.\r\n\r\nI intend making the search choices \"whole EPG/current bouquet/current channel\".\r\n\r\nI'm happy to implement this, but I have a question about what the default setting should be. For user convenience, I'd prefer the default to be \"current bouquet\". Backwards compatibility would argue for \"whole EPG\".\r\n\r\nDoes anyone (especially the oe-alliance reviewers) have opinions either way on this? Or even whether it's a good idea at all?"},"comment":{"url":"https://api.github.com/repos/oe-alliance/enigma2-plugins/issues/comments/231731674","html_url":"https://github.com/oe-alliance/enigma2-plugins/issues/86#issuecomment-231731674","issue_url":"https://api.github.com/repos/oe-alliance/enigma2-plugins/issues/86","id":231731674,"user":{"login":"prl001","id":7552983,"avatar_url":"https://avatars.githubusercontent.com/u/7552983?v=3","gravatar_id":"","url":"https://api.github.com/users/prl001","html_url":"https://github.com/prl001","followers_url":"https://api.github.com/users/prl001/followers","following_url":"https://api.github.com/users/prl001/following{/other_user}","gists_url":"https://api.github.com/users/prl001/gists{/gist_id}","starred_url":"https://api.github.com/users/prl001/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/prl001/subscriptions","organizations_url":"https://api.github.com/users/prl001/orgs","repos_url":"https://api.github.com/users/prl001/repos","events_url":"https://api.github.com/users/prl001/events{/privacy}","received_events_url":"https://api.github.com/users/prl001/received_events","type":"User","site_admin":false},"created_at":"2016-07-11T13:20:03Z","updated_at":"2016-07-11T13:20:03Z","body":"> Adapting a small part of skins wouldn't withheld me; that happens all the time. And (sometimes) progress and innovation takes it toll :) And then only for skins that actually have this plugin skinned, that don't use the embedded screen.\r\n\r\nChanging only `EPGSearchList` to use TemplatedMultiContent and leaving `EPGList` unchanged would mean an ugly copy/paste of code from `EPGList` into `EPGSearchList`. Changing `EPGList` to use TemplatedMultiContent and leaving `EPGSearchList` would mean a major rewrite of `EPGSelection`, all the list generation for all the different EPG layouts and all the skins for all those layouts.\r\n\r\n> But easy talking for me, as I would only have to do the skinning, not the actual coding.\r\n\r\nIt's not just the code that would need major changes; it would be al the EPG skins, too.\r\n\r\n> So what would be the next best solution that offers flexibility and would suite SD, HD & FHD skins, both full screen & partial screen?\r\n\r\nLet me have a go at a layout that will work with the current code and with half-screens on 1280-wide screens. 660 px is not drastically smaller than 1175, especially when there's quite a bit of wasted space in the Beyonwiz 1175-wide list layout."}}
{"actor":{"display_login":"prl001"}}