forgot to reply to all. Sorry.
On Tue, Aug 11, 2009 at 2:47 AM, Tor Lillqvist wrote:
>> Any ideas how to make this work?
>
> Install the svg pixbuf loader (and its dependencies), and edit the
> gdk-pixbuf.loaders file (or use gdk-pixbuf-query-loaders).
>
> See http://ftp.gnome.org/pub/GNOME/binari
> Any ideas how to make this work?
Install the svg pixbuf loader (and its dependencies), and edit the
gdk-pixbuf.loaders file (or use gdk-pixbuf-query-loaders).
See http://ftp.gnome.org/pub/GNOME/binaries/win32/librsvg/2.26/ for
Windows binaries for the svg pixbuf loader. You will have to trawl
a
I have set up the svg pixbuf loader according to the instructions here
http://www.mail-archive.com/gtk-app-devel-list@gnome.org/msg11731.html,
including editing the gdk-pixbuf.loaders file and gathering all
dependencies. My application uses a named icon, "insert-link", and on
linux (Ubuntu) this au
I think I might just have to go with your idea and store the entire
array of current values before I check for user-changes. Like I said,
this isn't a small chunk, but so what. It sucks, it's a kluge, but
allowing the hscale to move forward the then forcing it back will (or
should) work, and that
It's not the original data that I can't hold onto, it's the user-changed data
I'm loosing. I have the original at my disposal freely. It's not in a
database, but it's in a very, very, very gimungous shared memory segment with
lookup functions, and just like in a database, these are arrays of s
The last one is easy to answer: there are lots of fields to work with,
and many times, records are shown in a parent-child relationship. The
lots of fields makes it easy for the user to forget if they've made a
change. The parent-child relationship makes it meaningful to have a
parent set of entr
Boggess Rod wrote:
> BTDT. Won't work because by then, the user-value I'm trying not to
> loose would already be lost.
Guess I don't understand the problem, then, as I don't see why this
would be if you kept track of it in an external variable between
callbacks. Maybe a very small, self-containe
On Mon, Aug 10, 2009 at 02:52:56PM -0400, Boggess Rod wrote:
> BTDT. Won't work because by then, the user-value I'm trying not to
> loose would already be lost.
It would not if you kept the original value elsewhere as suggested.
> I would have thought this was a somewhat popular function, especi
BTDT. Won't work because by then, the user-value I'm trying not to
loose would already be lost.
I would have thought this was a somewhat popular function, especially
when processing records from a database. But I don't seem to know what
to search for. I can seem to find one single example anywh
Boggess Rod wrote:
> I guess I wasn't clear. The messagebox is working fine. It returns
> whether the user clicked Ok or Cancel. I'm calling the
> gtk_dialog_run(...) from within the callback of the
> on_hscale_valuechanged(...) (or _changevalue) event handler. It's the
> hscale's event handler
Michael Torrie wrote:
> Well inside a callback you can return TRUE which stops signal
> propagation right here. Or FALSE, which lets it continue. So you could
> do it two ways. One would be to to display a GtkDialog, and use
> gtk_dialog_run() from within your callback [1]. The other would be t
Boggess Rod wrote:
> Can someone point me to some example code in Gtk that intercepts a
> signal, prompts the user, and either continues or aborts the signal,
> depending on user response? A button wouldn't do this, but I'm sure
> there are other widgets that would. I've Googled everything I can
I've got a bunch of entry boxes and an HScale widget. If the user
changes something on the form and clicks the HScale Widget before
clicking the save button, I popup a message box. If the user clicks Ok,
the HScale should ignore the changes and procede. If the user clicks
Cancel, the HScale shou
13 matches
Mail list logo
