On Mon, Aug 16, 2010 at 12:15 PM, Aapo Rantalainen <span dir="ltr"><<a href="mailto:aapo.rantalainen@gmail.com" target="_blank">aapo.rantalainen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> I see we have a few apps (especially ports and stuff using SDL) that do not<br>
> know how to suspend themselves and therefore it fails the QA. Now, the problem<br>
> is that often it is non-trivial to fix/support this, and it's not that easy to<br>
> point people to the right resources (due to the number of technologies<br>
> involved). Often the people involved are not the authors, just maintainers, so<br>
> their understanding of the inner workings/event loops of the apps is rather<br>
> limited, making things even more difficult.<br>
<br>
</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Does it mean original writer is using SDL wrongly?<br>
<br>
Is this suspend-issue something that (all) upstream should be informed<br>
and should they fix it?<br>
(Is this relating overall power usage and 'green-computing'?)<br></blockquote><div><br></div><div>Sadly I don’t know SDL at all, but it is clear that this has nothing to do with upstream - </div><div>on the desktop, there is no ’rule’ that apps should pause or stop if they lose focus or </div>
<div>another app claims focus (like often in our case the phone app or IM), it is even</div><div>customary to use a button press to pause. On top of that, the mechanism for </div><div>detecting this (going to background, screen turning off, lock button</div>
<div>pressed) would be Maemo specific so would likely never go upstream anyway.</div><div><br></div><div>Best regards,</div><div>Attila</div>
<br>