Hello.
I'm not experienced in gtk+ too. But I think you should connect
call of your function to some gtk event (g_signal_connect). Updating
progress bar you should connect to timeout or idle event (read about
g_timeout_add, g_idle_add). And in your function call:
while
Once gtk-main is called, it waits for something to do.
Normally this would be a result of some user interaction.
Either use a Run button to get some action or use a timer to interrupt
and start the processing.
Rgds Bill
On 17/04/11 16:15, Maklakov Andrey wrote:
Hello.
I'm not
On Sat, Apr 16, 2011 at 5:04 AM, Marco net...@lavabit.com wrote:
Where should I put the function
DoSomeStuff()? I attached a minimal example, it's written in lua.
You should call DoSomeStuff() immediately before gtk.main(), but at
the end of the loop in DoSomeStuff you will need to add this
On Fri, Apr 15, 2011 at 7:45 PM, Alexander Larsson al...@redhat.com wrote:
On Fri, 2011-04-15 at 08:49 -0700, Kevin Fox wrote:
On Fri, 2011-04-15 at 06:01 -0700, Alexander Larsson wrote:
On Fri, 2011-04-15 at 14:18 +0200, Damjan Jovanovic wrote:
Of course, some files are inherently
On Apr 17, 2011, at 1:33 AM, Damjan Jovanovic wrote:
On Fri, Apr 15, 2011 at 7:45 PM, Alexander Larsson al...@redhat.com wrote:
On Fri, 2011-04-15 at 08:49 -0700, Kevin Fox wrote:
On Fri, 2011-04-15 at 06:01 -0700, Alexander Larsson wrote:
On Fri, 2011-04-15 at 14:18 +0200, Damjan Jovanovic
Hi,
On Sun, Apr 17, 2011 at 12:23 AM, Kean Johnston kean.johns...@gmail.com wrote:
For simplicity, suppose that your all-in-one-files have the extension
.glick. Suppose also that we have a per-user-per-system daemon
watching (relevant parts of, such as only ~/Downloads, ~/Desktop and
So, I've played with this now.
First, I created a test Glade file[1] rendering all the combinations.
Then I created a Glade file with the (IMO) correct rendering[2]. The
renderings show what combination is rendered and then render it using
a trick that guarantees the widgets get assigned their
