Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: mbp@lakisis.umd.edu (Mark Phillips)
Newsgroups: comp.sys.sun
Subject: Re: SunView question: positioning parts of a slider
Message-ID: <8902091345.AA15167@lakisis.umd.edu>
Date: 14 Feb 89 17:50:45 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 27
Approved: Sun-Spots@rice.edu
Original-Date: Thu, 9 Feb 89 08:45:10 EST
X-Sun-Spots-Digest: Volume 7, Issue 154, message 11 of 14

Thanks for the slider info.  As it turns out, I solved the problem some
time ago (the delay with submissions to Sun-Spots is really long!)  by
setting PANEL_SHOW_VALUE to FALSE and using a separate message item, which
gets updated with every call to the slider's notify proc, to display the
slider's value.  I set PANEL_NOTIFY_LEVEL to PANEL_ALL so the value gets
updated whenever the slider is moved.

This actually works very nicely, and I'm using it to implement a slider
which essentially is real-valued.  Of course, internally, the slider's
value is really an integer, but I can display it in whatever format I
want, which in my case is 1/10 of the value.  So my slider takes values
between 1.0 and 2.0.

>       Incidentally, it is not hard to implement a slider yourself
>  with a few message items containing the values and a pixrect that
>  understands click and drag events.

Wouldn't it be nice if you could define new items like this, and
attributes for them (like a typedef), and then create and manipulate them
with panel_create_item, panel_set, etc, just like all the "built-in" item?
But then again, wouldn't a lot of things be nice...!!

	--Mark

[[ The Sun-Spots delay varies.  Notice that this particular message took 5
days including a weekend.  I'm trying to keep it as small as possible (but
things tend to conspire against me).  --wnl ]]