11 May
2015
11 May
'15
11:55 a.m.
Hi,
I’ve launched my oldish project, and encountered an issue with new grapher. When one uses
#labelConversion: he has to define an axis label for a certain index of dataset. But in
latest Grapher this index can exceed the total number of dataset entries. While this is
not an issue for continuos data, I am experiencing problems when I want to graph readings
in a stacked manner. For example I have data readings taken in a different moment of time,
and I wan to label the index of a reading and it’s time, to give and idea where in time it
is, but when I’m asked about the label on 4 indices after my last reading I cannot put
there anything.
Uko
11 May
11 May
10:43 p.m.
Hi Yuriy,
Can you provide a code snippet please? It would help to really grasp the problem :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On May 11, 2015, at 5:55 AM, Yuriy Tymchuk
<yuriy.tymchuk(a)me.com> wrote:
Hi,
I’ve launched my oldish project, and encountered an issue with new grapher. When one uses
#labelConversion: he has to define an axis label for a certain index of dataset. But in
latest Grapher this index can exceed the total number of dataset entries. While this is
not an issue for continuos data, I am experiencing problems when I want to graph readings
in a stacked manner. For example I have data readings taken in a different moment of time,
and I wan to label the index of a reading and it’s time, to give and idea where in time it
is, but when I’m asked about the label on 4 indices after my last reading I cannot put
there anything.
Uko
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
12 May
12 May
10:37 a.m.
Ok, look at something like this:
| b ds items |
items := (100 to: 0 by: -5) asOrderedCollection.
b := RTGrapher new.
b extent: 500 @ 100.
ds := RTStackedDataSet new.
ds points: items.
ds y: #yourself.
ds barShape.
b add: ds.
b axisX
labelConversion: [ :index |
(items at: (index min: items size max: 1)) asString ].
b build.
b view
In my case I put time values on x axis. As you can see 0 in the end is really misleading.
In the previous axis of grapher last tick was placed right on the last element.
Uko
On 11 May 2015, at 22:43, Alexandre Bergel
<alexandre.bergel(a)me.com> wrote:
Hi Yuriy,
Can you provide a code snippet please? It would help to really grasp the problem :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On May 11, 2015, at 5:55 AM, Yuriy Tymchuk
<yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote:
Hi,
I’ve launched my oldish project, and encountered an issue with new grapher. When one uses
#labelConversion: he has to define an axis label for a certain index of dataset. But in
latest Grapher this index can exceed the total number of dataset entries. While this is
not an issue for continuos data, I am experiencing problems when I want to graph readings
in a stacked manner. For example I have data readings taken in a different moment of time,
and I wan to label the index of a reading and it’s time, to give and idea where in time it
is, but when I’m asked about the label on 4 indices after my last reading I cannot put
there anything.
Uko
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
3511
days inactive
3512
days old
2 comments
2 participants
participants (2)
-
Alexandre Bergel -
Yuriy Tymchuk