Video Highlander

[SteveGilvarry]

Yes that is right there can only be one. Rather than chop off heads, I have merged the two competing solutions for video storage. This is the raw merge so it will have issues, but I wanted to put this out there and see what people think.
Issues to be resolved

• Detect when camera is being recorded as h264 and don't use videoevent code
• Merge two competing UI options into one that works and can be merged to master.
• Fix the FIXME's in videostorage

This will break feature-h264-videostorage branch, but you have to break some eggs to make a cake.

[knight-of-ni]

Note that a div id of "videoEvent" is already being used in line 133. Probably should give this a different name.

[knight-of-ni]

Note that a div id of "videoEvent" is already being used in line 133. Probably should give this a different name.

[SteveGilvarry]

@connortechnology I don't think $Monitor is available here, well it doesn't seem to be defined when I debug it. But I am merging two branches so I may have clobbered something that loaded it. I know it was a while ago, but maybe you have branch still working and can check it.

[SteveGilvarry]

@connortechnology I don't think $Monitor is available here, well it doesn't seem to be defined when I debug it. But I am merging two branches so I may have clobbered something that loaded it. I know it was a while ago, but maybe you have branch still working and can check it.

[connortechnology]

I might have pushed this, but it was originally written by @mastertheknife . Seems to me that Monitor needs to be defined. Perhaps the line that defines it has been lost.

[SteveGilvarry]

No worries I pulled the required field in with the event query, which was already joining monitor table so easy to just add those new fields.

[SteveGilvarry]

No worries I pulled the required field in with the event query, which was already joining monitor table so easy to just add those new fields.