https://bugs.launchpad.net/tagger/+bug/1575552
On 27 April 2016 at 16:06, Olivier Tilloy <olivier.til...@canonical.com> wrote: > On Wed, Apr 27, 2016 at 4:15 PM, Gareth France <gareth.fra...@gmail.com> > wrote: > > I have now transferred a file directly onto the tablet and that will > read, > > this suggests that trying to read them directly off a screen is confusing > > the app. I have done the same with the codes I need to read and it > doesn't > > work. Inverted the colour, doesn't work. Other people here using android > or > > ios can read them just fine. I have attached one of these codes to the > bug. > > Bug link please? > > > > On 27 April 2016 at 11:26, Gareth France <gareth.fra...@gmail.com> > wrote: > >> > >> I'm on 10.1. I'm having to scan codes displayed on my desktop screen for > >> work. I've been looking everywhere but I haven't yet managed to find > one off > >> screen to try. They're everywhere until you need one! > >> > >> On 27 April 2016 at 11:23, Michael Zanetti < > michael.zane...@canonical.com> > >> wrote: > >>> > >>> Did you upgrade to OTA-10 or are you still on the initial release > >>> (OTA-9.5)? There were some issues in the initial release which > prevented > >>> some things like screenshotting (and with that prevented tagger from > >>> reading the image programmatically). > >>> > >>> > >>> > >>> On 27.04.2016 12:02, Gareth France wrote: > >>> > Any ideas why mine might not be? > >>> > > >>> > On 27 April 2016 at 10:51, Olivier Tilloy < > olivier.til...@canonical.com > >>> > <mailto:olivier.til...@canonical.com>> wrote: > >>> > > >>> > On Wed, Apr 27, 2016 at 11:47 AM, Gareth France > >>> > <gareth.fra...@gmail.com <mailto:gareth.fra...@gmail.com>> > wrote: > >>> > > I have raised another bug as I have discovered my inability to > >>> > decode QRs is > >>> > > a separate thing. I have tried using example codes found > online, > >>> > big and > >>> > > clear. I have tried taking a photo, cropping and using that > >>> > photo. Nothing > >>> > > decodes! On my phone it was effectively instant. I did randomly > >>> > decode the > >>> > > letter V from god only knows what when I wasn't even pointing > it > >>> > at a code > >>> > > yesterday. Can anyone else get this to work on their M10? > >>> > > >>> > Yes, it’s working fine for me here on a FHD M10, scanning the QR > >>> > code > >>> > on https://en.wikipedia.org/wiki/QR_code is almost instant. > >>> > > >>> > > >>> > > On 27 April 2016 at 10:06, Michael Zanetti > >>> > <michael.zane...@canonical.com > >>> > <mailto:michael.zane...@canonical.com>> > >>> > > wrote: > >>> > >> > >>> > >> > >>> > >> > >>> > >> On 27.04.2016 10 <tel:27.04.2016%2010>:06, Olivier Tilloy > wrote: > >>> > >> > On Wed, Apr 27, 2016 at 10:00 AM, Michael Zanetti > >>> > >> > <michael.zane...@canonical.com > >>> > <mailto:michael.zane...@canonical.com>> wrote: > >>> > >> >> > >>> > >> >> > >>> > >> >> On 27.04.2016 09 <tel:27.04.2016%2009>:37, Gareth France > >>> > wrote: > >>> > >> >>> This is on the M10, on my E4.5 tagger works beatifully. > >>> > >> >>> > >>> > >> >>> On 27 April 2016 at 08:34, Olivier Tilloy > >>> > >> >>> <olivier.til...@canonical.com > >>> > <mailto:olivier.til...@canonical.com> > >>> > >> >>> <mailto:olivier.til...@canonical.com > >>> > <mailto:olivier.til...@canonical.com>>> wrote: > >>> > >> >>> > >>> > >> >>> On Tue, Apr 26, 2016 at 10:22 PM, Gareth France > >>> > >> >>> <gareth.fra...@gmail.com > >>> > <mailto:gareth.fra...@gmail.com> > >>> > <mailto:gareth.fra...@gmail.com <mailto:gareth.fra...@gmail.com > >>> > >>> > wrote: > >>> > >> >>> > It seem that tagger is behaving weird, the image is > >>> > displayed > >>> > >> >>> the > >>> > >> >>> wrong way > >>> > >> >>> > up making it near impossible to centre on what you > >>> > want > >>> > to scan > >>> > >> >>> as > >>> > >> >>> it always > >>> > >> >>> > moves the opposite way and messes with your mind! > >>> > >> >>> > > >>> > >> >>> > I haven't been able to scan a single code yet, it > just > >>> > doesn't > >>> > >> >>> pick them up. > >>> > >> >>> > It was very quck on my phone so this surprised me. > Is > >>> > this > >>> > >> >>> known? > >>> > >> >>> I'm not > >>> > >> >>> > sure wher to look for a bug. > >>> > >> >>> > >>> > >> >>> You can look for existing bugs, and report a new one, > >>> > here: > >>> > >> >>> https://bugs.launchpad.net/tagger. > >>> > >> >>> > >>> > >> >>> On which device are you seeing this btw? I’ve tested > the > >>> > E4.5 and > >>> > >> >>> the > >>> > >> >>> MX4, and I’m not observing anything wrong. > >>> > >> >> > >>> > >> >> > >>> > >> >> Actually this happens on all devices. Currently apps cannot > >>> > distinguish > >>> > >> >> between Landscape and InvertedLandscape (or Portrait and > >>> > >> >> InvertedPortrait). I can not fix that in the app until the > >>> > API > >>> > in the > >>> > >> >> platform is fixed. > >>> > >> > > >>> > >> > OK, I’m seeing it now. > >>> > >> > The obvious workaround is to hold the device in > >>> > portrait/landscape > >>> > >> > instead of inverted portrait/inverted landscape, right? > >>> > >> > > >>> > >> > >>> > >> Yes. Although I really don't like that workaround :) However, > >>> > the fix > >>> > >> for this is not straight forward. It's something to be fixed > in > >>> > Qt and > >>> > >> also requires to rework a "hack" that got introduced for the > >>> > camera-app > >>> > >> in qtubuntu. > >>> > >> > >>> > >> > >>> > >> > >>> > >> -- > >>> > >> Mailing list: https://launchpad.net/~ubuntu-phone > >>> > >> Post to : ubuntu-phone@lists.launchpad.net > >>> > <mailto:ubuntu-phone@lists.launchpad.net> > >>> > >> Unsubscribe : https://launchpad.net/~ubuntu-phone > >>> > >> More help : https://help.launchpad.net/ListHelp > >>> > >> > >>> > > > >>> > > >>> > > >>> > >> > > >
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
