Re: range inversion/mapping [patch]



On Thu, 22 Feb 2001, Jay Cox wrote:

> I have written a patch that implements the mapping via signals.
> 
> It has the minor problem that you can only connect one mapping
> function to it or else the calculations will be inconsistant
> between input mapping and output mapping.  This could be fixed
> if there were a way to guarantee that the inputmap and the
> outputmap signal handlers would be called in reverse order to
> each other.
> 
> Jay Cox
> jaycox gimp org

> +  void (* inputmap)  (GtkRange *range,
> +		      gfloat   *value);
> +  void (* outputmap) (GtkRange *range,
> +		      gfloat   *value);
> +

What about making these signals into:
  gfloat (*inputmap) (GtkRange *range, gfloat value);

This would be a lot more natural for most language bindings
(GTK_TYPE_POINTER is not very useful for language bindings).

James.

-- 
Email: james daa com au
WWW:   http://www.daa.com.au/~james/






[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]