On Wed, 14 Apr 2010 10:01:15 +0530
Nischal Rao wrote:
> Let me explain the entire scenario.
>
> I need to be listening to a socket for data from an external program.
> I do this using an infinite loop. Once i get the data, i call a
> function and after it returns I go back into infinite loop agai
Nischal Rao wrote:
> is there any way to listen to signals without calling gtk_main() (which
> never returns) ? If so, then i ll be able to get rid of
> threads(happily!!) I am new to glib threads and gnome signals.. i
> have just been following examples that i found on the net.
What kind of s
Let me explain the entire scenario.
I need to be listening to a socket for data from an external program. I do
this using an infinite loop. Once i get the data, i call a function and
after it returns I go back into infinite loop again.
While all this is happening I also need to listen to some sign
On Wed, 14 Apr 2010 00:13:38 +0530
Nischal Rao wrote:
> is there any way to listen to signals without calling gtk_main()
> (which never returns) ? If so, then i ll be able to get rid of
> threads(happily!!) I am new to glib threads and gnome signals.. i
> have just been following examples th
is there any way to listen to signals without calling gtk_main() (which
never returns) ? If so, then i ll be able to get rid of
threads(happily!!) I am new to glib threads and gnome signals.. i have
just been following examples that i found on the net.
Please help me. My requirement is that i
Nischal Rao wrote:
> the sample code is:
[..]
your use of threading doesn't make sense. All your threads are within a
lock, so you have three threads (main + two threads) but they can never
execute any instructions in parallel, because they all wait for the
global gdk lock.
Everything you want to
the sample code is:
#include "myheader.h"
int main(int argc, char ** argv)
{
GThread *l_th1, *l_th2;
g_thread_init(NULL);
gdk_threads_init();
gtk_init(&argc,&argv);
initCommandParser();
initCurrentManager();
initWindowManager();
l_th1 = g_thread_create(_gtkthread,N
> By the way, I had never programmed using glib threads before. Is the threads
> part of the code I had sent earlier correct?
If you want people to actually test your code, you do need to show a
*complete* compilable and *minimal* test case.
In general, it's best to avoid threads. For some reason
On Tue, 13 Apr 2010 01:01:15 +0530, Nischal Rao
wrote:
>> Is the
>> threads part of the code I had sent earlier correct?
I haven't seen the code yet. It could be me, but the mailing list software
probably scrubs attachments. Most folks just post as inline text.
--
www.thomasstover.com
__
Not sure if it's just me, but I can't see the attachment. For things like fseek
and fclose, you might want to look at the gio library
(http://library.gnome.org/devel/gio/stable/) which is included along with glib.
On Tue, 13 Apr 2010 00:21:44 +0530
Nischal Rao wrote:
> I just noticed... the co
the problem still persists. :(
my assumption was wrong
On Tue, Apr 13, 2010 at 12:43 AM, Nischal Rao wrote:
> I got the problem!
>
> The thing is, before calling the prepareGrammar() function i am calling a
> function, SPI_generateMouseEvent() which modifies the at-spi tree which is
> ac
I got the problem!
The thing is, before calling the prepareGrammar() function i am calling a
function, SPI_generateMouseEvent() which modifies the at-spi tree which is
accessed by prepareGrammar, i.e., i was accessing the tree while it was
being modified by another external program. All i need to
I just noticed... the code sometimes works and sometimes doesn't work(the
code doesn't go to completion which kind of confirms that there is thread
lock problem).
There doesn't seem to be an error in other parts of the code because the
code works fine when i comment the file writing part(i.e., pre
It would be *much* easier to help you if you could show us some actual
code that works strangely for you. A minimal but complete sample
program, thanks. Now it is very hard to understand what you mean.
--tml
___
gtk-app-devel-list mailing list
gtk-app-de
On Mon, 12 Apr 2010 21:25:44 +0530, Nischal Rao
wrote:
> the files are coming empty. I suspect this is happening because of
thread
> lock problems...
>
>
Have you tried a "flush" operation. ie fflush() or g_io_channel_flush()?
Beyond that we would need to see some sort of code example.
--
ww
On Mon, Apr 12, 2010 at 8:33 PM, Thomas Stover wrote:
> 1) you mean glib threads right? (maybe there is a gnome thread?)
>
yes... i mean glib threads.
> 2) you're going to want to use glib based functions like io channels
> instead of stdio (for regular files at least)
> 3) "don't seem to work"
2010/4/12 Nischal Rao :
> Hi,
>
> Within a gnome thread i need to read as well as write to a file. I tried
> using the regular fprintf() etc but they don't seem to work.
> Can somebody please help me out since I am new to gnome threads.
see if you can use the GIO _async() calls, they use threads i
1) you mean glib threads right? (maybe there is a gnome thread?)
2) you're going to want to use glib based functions like io channels
instead of stdio (for regular files at least)
3) "don't seem to work" is not enough information for anyone to help you
4) you also need a real reason to be using thr
Hi,
Within a gnome thread i need to read as well as write to a file. I tried
using the regular fprintf() etc but they don't seem to work.
Can somebody please help me out since I am new to gnome threads.
Thanks in advance.
--
regards,
Nischal E Rao
blogs.sun.com/nischal
Join RVCE OSUM at http:/
19 matches
Mail list logo
