Adam Shaw

Reported by `adamrshaw` on 2013-08-14 02:04:34 - **Labels added**: Type-Feature - **Labels removed**: Type-Enhancement

``` Issue 2103 has been merged into this issue. ``` Reported by `adamrshaw` on 2013-08-25 00:24:28

``` NOTE: we might want to allow multiple "rows" of controls (see issue 2103) ``` Reported by `adamrshaw` on 2013-08-25 00:25:09

``` Issue 2213 has been merged into this issue. ``` Reported by `adamrshaw` on 2013-08-25 07:42:55

``` yeah, this feature might be good to implement at the same time as http://code.google.com/p/fullcalendar/issues/detail?id=143 ``` Reported by `adamrshaw` on 2010-08-26 04:24:37

``` I implemented the above suggestion like so: else if(match = buttonName.match(/^{(\w+):(.+)}$/)) { if(typeof(options[match[2]]) == "function") { buttonClick = options[match[2]]; } else if(typeof(window[match[2]]) == "function") { buttonClick = window[match[2]]; }...

``` i think scrolling (.focus() ?) to the next event in week view could be better... and yes, if there is not why not to the current hour... ``` Reported...

``` has anything changed in v2? is there a way of adding custom HTML to the header without changing fullcalendar? ``` Reported by `patrickwasp` on 2014-04-09 23:43:15

Reported by `adamrshaw` on 2010-10-07 22:18:33 - **Status changed**: `Maybe`

``` @stephenh1988 has made an implementation of this in his fork: https://github.com/arshaw/fullcalendar/pull/70 I have not tested it nor investigated its compatibility with v2, but its worth checking out. ``` Reported...