Re: Opie Desktop version

"Rajalakshmi Raghavan" <[email protected]> Tue, 8 Apr 2008 18:32:50 +0800
Newsgroups gmane.comp.handhelds.opie
Message-ID <[email protected]>
--===============1149359828==
Content-Type: multipart/alternative; 
	boundary="----=_Part_19119_1034660.1207650770243"

------=_Part_19119_1034660.1207650770243
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Paul!

I must say, all your tips were really helpful! I finally managed to get Opie
1.2.0 to work! Removed all those applets!

But, I have the same problem opening Opieplayers in Opie 1.2.0 as well as
1.2.3. I get this infinite number of Warning messages like I mentioned
earlier. Your idea about the player searching the filesystem was great. I
debugged the playlistwidget.cpp and managed to find the line that was
causing the scanning and managed to prevent it.. the line was as follows:

playLists = new FileSelector( "playlist/plain;audio/x-mpegurl", LTab,
"fileselector" , FALSE, FALSE);

I just changed it to playLists = NULL.

Good news is that the old error is solved but now there is a new error!! Now
Opieplayer says: Opieplayer was terminated due to signal code SIGSEGV

Sigh... Any ideas?

Thanks alot!

Sincerely,
Raji

On Thu, Mar 27, 2008 at 8:21 PM, Paul Eggleton <
[email protected]> wrote:

> On Thursday 27 March 2008, you wrote:
> > 1. As for the segmentation fault, just now I disabled all applets from
> the
> > .config file and tried running qpe. However, I could not get rid of the
> > segmentation fault.
>
> Ah, right. You may also need to delete .so files in the plugins/applets/
> directory.
>
> > 2. The Opieplayer issue that I have.. Do you know which part of the
> codes
> > is responsible for the scanning of the filesystem, that u mentioned?
> > Perhaps, if I could disable that, would it work?
>
> Have a look in playlistwidget.cpp, I think most of the scanning is done in
> there. You may find you can add or uncomment some odebug() statements to
> see
> where it is spending all of its time.
>
> Cheers,
> Paul
>

------=_Part_19119_1034660.1207650770243
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Paul!<br><br>I must say, all your tips were really helpful! I finally managed to get Opie 1.2.0 to work! Removed all those applets!<br><br>But, I have the same problem opening Opieplayers in Opie 1.2.0 as well as <a href="http://1.2.3.">1.2.3.</a> I get this infinite number of Warning messages like I mentioned earlier. Your idea about the player searching the filesystem was great. I debugged the playlistwidget.cpp and managed to find the line that was causing the scanning and managed to prevent it.. the line was as follows: <br>
<br>playLists = new FileSelector( &quot;playlist/plain;audio/x-mpegurl&quot;, LTab, &quot;fileselector&quot; , FALSE, FALSE);<br><br>I just changed it to playLists = NULL.<br><br>Good news is that the old error is solved but now there is a new error!! Now Opieplayer says: Opieplayer was terminated due to signal code SIGSEGV<br>
<br>Sigh... Any ideas?<br><br>Thanks alot!<br><br>Sincerely,<br>Raji<br><br><div class="gmail_quote">On Thu, Mar 27, 2008 at 8:21 PM, Paul Eggleton &lt;<a href="mailto:[email protected]">[email protected]</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Thursday 27 March 2008, you wrote:<br>
&gt; 1. As for the segmentation fault, just now I disabled all applets from the<br>
&gt; .config file and tried running qpe. However, I could not get rid of the<br>
&gt; segmentation fault.<br>
<br>
</div>Ah, right. You may also need to delete .so files in the plugins/applets/<br>
directory.<br>
<div class="Ih2E3d"><br>
&gt; 2. The Opieplayer issue that I have.. Do you know which part of the codes<br>
&gt; is responsible for the scanning of the filesystem, that u mentioned?<br>
&gt; Perhaps, if I could disable that, would it work?<br>
<br>
</div>Have a look in playlistwidget.cpp, I think most of the scanning is done in<br>
there. You may find you can add or uncomment some odebug() statements to see<br>
where it is spending all of its time.<br>
<br>
Cheers,<br>
<font color="#888888">Paul<br>
</font></blockquote></div><br>

------=_Part_19119_1034660.1207650770243--

--===============1149359828==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Open Source User Interface and Apps built on Qt Embedded
Opie mailing list
[email protected]
https://handhelds.org/mailman/listinfo/opie

--===============1149359828==--