When was the last time this worked for you?  Was it a _really_ long time ago
(e.g. before mid-2010?)

-Vic



On Thu, Feb 17, 2011 at 6:59 PM, Vic Fryzel <[email protected]> wrote:

> Oh, I didn't realize you meant you'd committed it already.  Will check.
>
> -Vic
>
>
>
> On Thu, Feb 17, 2011 at 6:48 PM, pamela fox <[email protected]> wrote:
>
>> I put in the change I mentioned to assume the first row is a header row,
>> and to not use getColumnLabel anymore.
>> You can see the change in the code starting around line 100 here:
>> http://code.google.com/p/pamelafox-samplecode/source/detail?r=418#
>>
>> Is getColumnLabel still meant to work for spreadsheets gadgets? I looked
>> briefly through samples and didn't find one that used it.
>> I just want to follow best practice for how to deal with specification of
>> header rows in gadgets, and from the change in the UI to no longer have
>> users specify number of header rows, it seems like maybe there's a new best
>> practice.
>>
>> - pamela
>>
>> On Fri, Feb 18, 2011 at 9:19 AM, Vic Fryzel <[email protected]> wrote:
>>
>>> Hey Pamela,
>>>
>>> I can't reproduce what you're reporting.  The header row is assumed for
>>> me.
>>>
>>> See screenshot.
>>>
>>> -Vic
>>>
>>>
>>>
>>> On Thu, Feb 17, 2011 at 5:04 PM, pamela <[email protected]> wrote:
>>>
>>>> Hey there-
>>>>
>>>> My gadget is no longer working as expected. The gadget is described
>>>> here:
>>>>
>>>> http://blog.pamelafox.org/2009/05/how-to-convert-google-spreadsheet-into.html
>>>>
>>>> The spreadsheets gadgets interface used to present a "number of header
>>>> rows" setting for gadgets,
>>>> and then the header labels would be made available via the
>>>> getColumnLabel function from the API.
>>>> Now, there is no such setting, and I'm getting an empty string returned
>>>> from that function.
>>>>
>>>> I will assume 1 header row for now to get a quick fix in, but would like
>>>> to know what the recommended strategy is for header rows now, given the
>>>> apparent UI/API changes.
>>>> Thanks!
>>>>
>>>> - pamela
>>>>
>>>
>>>
>>
>

Reply via email to