You're welcome. On Thursday, September 27, 2012 10:13:44 AM UTC-4, Gizamo wrote: > > Ah ha. That makes much more sense than what I was trying to do.. Don't > bother reviewing the old code again, I can certainly get this latest > version to fit my needs. It is awesome. Thank you for all of your help, and > thanks for helping others too. I'm sure they appreciated it, and a few of > your past projects were also great reference tools for me. > > On Tuesday, September 25, 2012 12:30:56 PM UTC-6, asgallant wrote: >> >> It takes a bit of tweaking, less on the selector and more on the >> structure of the rest of the code, to make it work: >> http://jsfiddle.net/asgallant/LWDP4/12/. Basically, you have to track >> which columns you are using and which options need to change based on the >> columns. >> >> While I was working on that, I noticed issues with the way you had set up >> things before, but I can't recall precisely what they were. If you decide >> not to use this, I'll go over your other code again. >> >> On Monday, September 24, 2012 6:42:01 PM UTC-4, Gizamo wrote: >>> >>> InterpolateNulls and the focusTarget:Category behaviors are exactly what >>> I needed. I was unaware of InterpolateNulls, and the focusTarget behavior >>> wasn't working earlier because I did not put the x values in proper order. >>> I had done one series and then the next, and they had overlapping x >>> coordinates... Anyway, that part all works great now, and using >>> (x,y) coordinate pairs was indeed unnecessary and impractical. You can see >>> it all working here: http://jsfiddle.net/LWDP4/8/ >>> >>> I looked through your CategoryFilter/SeriesSelector code, but I couldn't >>> figure out how to tweak it to select both blue and gray lines. The 2nd axes >>> in my chart is also causing some other problems, and I couldn't seem to >>> solve them either.. For example, if selectMultiple is set to True, and I >>> remove the series1, the data in column1 is deleted and the data from >>> column2 is assigned to column1 - the result is that my first gray line >>> becomes my last blue line, and it is now set to axes y1 instead of y2. >>> There are also issues when filtering series and switching among the various >>> units.. Oh, and if I set selectMultiple to False, any selected series is >>> assigned to the y1 axes. You can see it here: >>> http://jsfiddle.net/LWDP4/9/ >>> >>> Lastly, I found this code: http://jsfiddle.net/gTxkN/8/, which showed >>> me how to use the column number to select a series instead of the column >>> label. This is good for me because I had to remove the columns labels to >>> get the tooltip formatted the way I wanted.. Anyway, I plugged that code >>> into my chart, but it has the same/similar issues with the second axes in >>> my chart. See: http://jsfiddle.net/LWDP4/10/ >>> >>> Thanks again. The stuff we have working is awesome. >>> >>> On Tuesday, September 18, 2012 5:41:00 PM UTC-6, Gizamo wrote: >>>> >>>> Hello. I'm trying to make something similar to this line graph: >>>> http://jsfiddle.net/LuP4K/ >>>> >>>> The actual chart layout I'm trying to replicate is here: >>>> http://wkfluidhandling.com/media/images/performance-curves/psu060-performance-curves-665x435.png >>>> (but I'd like to use only Standard or Metric units and allow the user to >>>> choose whichever they prefer with a toggle button). >>>> >>>> Anyway, it was simple enough to setup in Highcharts, but I can't seem >>>> to figure out how to create a GoogleCharts version of it (in part because >>>> I >>>> am struggling with the API features/language). Can someone please get me >>>> started in the correct path? >>>> >>>
-- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/xT9dh7mECCIJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
