Hi Mark,

I think you are right.

If you look at
http://people.csail.mit.edu/dfhuynh/projects/timeline-exhibit/filtered-sources.js
line 16 (also counting blank line) you see:
onAddMany: function() { console.log("here"); self._onAddMany(); },
Just remove the console.log("here"); from this line so that is reads:
onAddMany: function() { self._onAddMany(); },

Only a couple of months ago I ran into exactly the same, but I already
completely forgot about it. Wish I could upgrade my memory as I can
with my computer.

Michiel

On Apr 14, 12:14 am, mleden <[email protected]> wrote:
> Thanks Michiel, I tried removing the ViewPanel but no luck.  Actually,
> I now think the problem is directly to do with the FilterEventSource
> functionality.
>
> If you go to the example for that 
> functionality:http://people.csail.mit.edu/dfhuynh/projects/timeline-exhibit/timelin...
> Input any value into the Search box.  The browser will return an error
> identical to the one that I am seeing when selecting any value from
> any facet.
>
> Any other thoughts?
>
> Thanks again,
> -Mark
>
> On Apr 12, 2:04 pm, Michiel <[email protected]> wrote:
>
> > Hi Mark,
>
> > Explaining what it console is is easy. Most developers work with
> > Firefox as their browser. There is a very useful extension to Firefox
> > called Firebug. It helps to find bugs. Firebug comes with a console
> > (just an window that displays messages), so during development a
> > developer typically writes useful internal info to this console.
> > Ordinary users have no use for the console and when the code is ready
> > for release, all calls to the console are often removed.
>
> > That is the theory. Exhibit uses the console via SimileAjax.Debug.log.
> > In trunk this is called at several places. The list-facet uses it, but
> > other facets don't. However more likely it is the call in view-
> > panel.js that is spoiling your exhibit. If creation of the view fails,
> > SimileAjax.Debug.log is used. Have you tried to run your exhibit not
> > with a viewpanel, but just with only the timelineview?
>
> > Michiel
>
> > On Apr 9, 7:52 pm, mleden <[email protected]> wrote:
>
> > > Hi,
>
> > > I'm using Exhibit and including the Timeline extension.  However, it
> > > seems that after I implemented autowidth (to size each band according
> > > to the amount of data points in each band), I'm now seeing a browser
> > > error whenever I make a selection on a facet.  It does not appear to
> > > matter which of the 4 facets I select or which of the values in those
> > > facets.
>
> > > In IE 8, the browser alert window displays:
> > > Caught exception: undefined
> > > Details: 'console' is undefined
>
> > > In FF 3.6.3, the browser alert window displays:
> > > Caught exception: undefined
> > > Details: ReferenceError: console is not defined
>
> > > (Another Timeline on the same page, using the same data, does not have
> > > the problem.  AFAIK, the only significant differences between the two
> > > are the use of more bands and the use of autowidth.)
>
> > > Unfortunately, it's inside the firewall and so I cannot point to a
> > > public URL.
>
> > > Has anyone seen something similar or, perhaps, know what might be the
> > > cause?
>
> > > Thank as always,
> > > -Mark

-- 
You received this message because you are subscribed to the Google Groups 
"SIMILE Widgets" group.
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/simile-widgets?hl=en.

Reply via email to