View Single Post
Copernicus's Avatar
Posts: 1,986 | Thanked: 7,698 times | Joined on Dec 2010 @ Dayton, Ohio
#684
Originally Posted by sixwheeledbeast View Post
IMO for maximum data capture a link to...

http://wiki.maemo.org/Pierogi_Device...atible_Devices

...should be added to Pierogi some how (menubar?).
Hmm. Yeah, something on the menubar seems easiest. Certainly, I can add it to the About or Documentation pages instantly (although I've got so much work to do on the documentation now, I'm kind of scared to even touch it). But it'd be interesting to try and fit the link somewhere on the Edit Keyset dialog (along with the device info known for that keyset). I will take a look.

Unless there is another easy "in-app" way of collecting this data?
Hmm. The only things I could think of off the top of my head all involve Pierogi making a call to an external server, and QtIrreco has shown me the dangers of that. But I should at least allow the user to add their own data for themselves. I need to do some more thinking here as well.

FYI liking the new layout for the scan panel although I am still getting trouble pausing and resuming the scan.
When this happens reverse and fast fwd also stop functioning.
If I can provide any more data I will using the latest 1.1.10 with the triax update.

Edit:-
It seems to be pressing the top four buttons while scanning kills the auto-scan feature.
Drat, you're right. The manual keys apparently aren't checking whether an automated scan is in progress, even though I set them up to work with an automated scan that is paused. (And I keep pushing up code without doing enough testing... )

As previously mentioned it's hard to get debug info.
/opt/pierogi/bin/pierogi
Spits out boxes in app with rubbish
Yeah, I've not yet figured out why my exception handler keeps losing all of its string data, gotta get that fixed too.

I'll get some more fixes up asap. Thanks!
 

The Following 3 Users Say Thank You to Copernicus For This Useful Post: