I think that's a wonderful idea.
{pe'i le sibdo ku xmagu} (pardon me if my lojban is horrible; I'm
practicing).
On Mon, Aug 16, 2010 at 8:19 AM, Andrew U. Frank
fran...@geoinfo.tuwien.ac.at wrote:
may i suggest that the description of the package, where it lists the
depreciated functions,
may i suggest that the description of the package, where it lists the
depreciated functions, give also a hint, how the function should be
replaced. i often hit the wall of depreciated functions when i try to
use a packaged not having been compiled for a while and i have to
replace the functions.
I recently started playing around with gtk2hs.
I noticed that `onClicked`, `afterClicked`, etc. functions have been
deprecated, presumably in favor of the `on` and `after` functions in the
Glib signals module, but I couldn't find a collection of the appropriate
signals to replace the
You mean something like buttonPressEvent [1]?
on button buttonPressEvent
You can define signals, the constructor is exposed.
[1]
http://www.haskell.org/gtk2hs/docs/current/Graphics-UI-Gtk-Abstract-Widget.html#v%3AexposeEvent
On Fri, Jul 16, 2010 at 11:36 AM, Alex Rozenshteyn
More like buttonActivated [1].
Has it been decided that button-specific events are going to be deprecated
in favor of their general widget equivalents, with buttonActivated being an
(IMO) awkward title for buttonClicked?
[1]
