|
2010-10-08
, 09:42
|
Posts: 1,994 |
Thanked: 3,342 times |
Joined on Jun 2010
@ N900: Battery low. N950: torx 4 re-used once and fine; SIM port torn apart
|
#542
|
|
2010-10-10
, 17:59
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#543
|
|
2010-10-10
, 19:49
|
Posts: 252 |
Thanked: 252 times |
Joined on Nov 2009
|
#544
|
No, I've concluded that OpenGL does the job and really it doesn't look like it adds much to the startup time.
It would certainly be useful for startup time to move the GStreamer pipeline setup, etc., to a thread so that the UI is brought up sooner. I'll take a look at this.
The Following User Says Thank You to dragly For This Useful Post: | ||
|
2010-10-11
, 14:59
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#545
|
I'll try to debug some more myself and see if I can figure out why there is some delay between the scan finishes and the results window is shown. Unless you've found anything on this, lardman?
The Following User Says Thank You to lardman For This Useful Post: | ||
|
2010-10-11
, 15:08
|
Posts: 252 |
Thanked: 252 times |
Joined on Nov 2009
|
#546
|
The one thing I spotted was that there's a 0.5s delay between the scan finishing and the plugin list being populated. The plugins are asked every 0.5s whether they can handle the barcode in question (ResultsWindow::checkPlugins()), and originally the timer callback was used to do the first call. I've commited a fix for this by simply calling the checkPlugins() immediately as the timer is setup.
I will do some more digging to see what else might be causing problems. Is the results window created at startup? It might be worth having it loaded and hidden to make the transition quicker (though this would cause slowdowns at startup - argh! )
The Following User Says Thank You to dragly For This Useful Post: | ||
|
2010-10-11
, 15:26
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#547
|
|
2010-10-11
, 18:57
|
|
Posts: 152 |
Thanked: 53 times |
Joined on Dec 2009
@ West Virginia
|
#548
|
|
2010-10-16
, 16:21
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#549
|
The Following User Says Thank You to lardman For This Useful Post: | ||
|
2010-10-18
, 12:40
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#550
|
The Following User Says Thank You to lardman For This Useful Post: | ||
Sorry about the lack of updates from my side. Been a bit busy, and it seems like maemo.org didn't want to notify me about new replies to this thread before today.
Just wanted to point out that I messed around with the overlay stuff for quite some time before going down the OpenGL path. The problem is that the xvimagesink overlay, as lardman points out, doesn't behave like expected. I experienced two outcomes which neither were positive. Either xvimagesink took over the whole window, like lardman wrote about just now, or the overlayed buttons or icons got a black box background.
If we figure this out without using OpenGL, it would be the very best solution. But if I'm not wrong, the FCamera app has these problems as well. The overlay there is cluttered with a black box background on all controls.
I guess we have to decide if we want smooth camera movement or want to avoid black boxes around the controls. Personally, I find the boxes very ugly, but if the OpenGL method still is giving bad performance even after lardman's latest improvements, I guess it might be better to go with performance.
What do you guys think?
dragly.org