Hello!
Context: https://bitbucket.org/p2t2p/gtkcombodemo/src/19be8dfe788c1aec1
a5384eb107facaa38e121ff/main.js?at=master=file-view-default
TL;DR
GTK+ renders ComboBox popup off-screen if the item is too low in the
list.
Help needed:
* Please confirm if it is a bug or if there is such a bug.
he CSS specification in the interactive debugger and the
background color reappears as it is intended.
I assume this triggers a reload/reapplication of the CSS.
Could that be a GTK bug? It appears as a rendering issue. When the
background appears black GTK+ Inspector reports
the 'background-colo
Zeeshan Ali wrote:
Hello,
On Tue, 22 Feb 2005 15:22:50 +0100, Stefan Kost [EMAIL PROTECTED] wrote:
Are you sure?
Yeah I am sure and thats why i suspect that it may be pointing to a
bug in gtk+. Why don't you try it youself? Shouldn't take 15 mins.
:)
Hi :)
When you create main loop
Zeeshan Ali ha scritto lo scorso 23/02/2005 10:31:
[...]
Yep, in a software of mine that is for ATM machines. You mean to
ask why i am using both the GMainLoop and gtk_main* in the same
software, right? At one hand i dont want to bring in gtk+ (glib only)
into the card-reader interfacing module
Zeeshan Ali wrote:
You may call it a nessecity of my laziness :)
Sure, L:) Laziness is great power and the reason of why there're so many
programming tools and libs avalaible.
BTW, you can debug deadlocks with gdb. You just need to attach it to
running process.
1. Compile program with '-g'
Hello,
Please, forgive my OT question, but I'm going to start a gtk+ project
involving the use of a smart card reader and I'd very happy to know your
suggestions about linux supported hardware.
Welcome to the gang! Sorry to dissappoint you but I too am very
new to all this. So far i've
On Wed, 2005-02-23 at 14:31 +0500, Zeeshan Ali wrote:
Hello,
On Wed, 23 Feb 2005 10:12:07 +0200, Olexiy Avramchenko
[EMAIL PROTECTED] wrote:
When you create main loop with NULL as context parameter, main loop gets
shared default context. Before you create your main loop, default
context
program that
re-produces the same problem. It seems more like a bug in the gtk+
rather than my logic. Please have a look at it and tell me it that's
the case so I can file it as a bug. I just dont want to file another
'NOT A BUG
Hello,
Hmm.. I thought that email with attachments goes through the
moderation. Anyway, I have uploaded it here:
http://www.geocities.com/zeelists/thread-problem.c . Kindly have a
look at it. Thanks.
___
gtk-app-devel-list mailing list
Hello,
On Tue, 22 Feb 2005 15:22:50 +0100, Stefan Kost [EMAIL PROTECTED] wrote:
Are you sure?
Yeah I am sure and thats why i suspect that it may be pointing to a
bug in gtk+. Why don't you try it youself? Shouldn't take 15 mins.
:)
___
gtk-app
Hello,
In a gtk+ app of mine, i was facing strange dead-locks problems. I
was astonished to see that just removing the call to gdk_threads_init,
the problems vanished. I am attaching a sample test program that
re-produces the same problem. It seems more like a bug in the gtk+
rather than my
11 matches
Mail list logo
