Functions renaming, dead code removal, simplifications and various resizing fixes.

Fixes #3364 (big bug on buttons)
It is not possible to click the same button twice in a row (while the
script is actually running), but other buttons can be clicked.

Fix #3370

Signed-off-by: Jean-Philippe André <jpeg@videolan.org>

Signed-off-by: Jean-Philippe André <jpeg@videolan.org>

Partial fix for #3304

Avoids confusion between dialog:close() and the "close()" hook
Partially fix #3304

Fix #3375

Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

arm_neon: fix the color conversion to use the actual pitch of the pictures instead of trying to guess it.

Signed-off-by: Christophe Mutricy <xtophe@videolan.org>

Close #3414

Ref #3414

Close #3408 (blocker)
Close #3245 (blocker)

the playlist control entirely redefines key processing (arrows, enter, ...).
Yet, for keys not processed, forwarding them to vlc core is desirable.
For instance, that enables n(ext) and p(revious) when focus is on the playlist,
which is something users can expect to be working.

This was leading to a crash when using --no-keyboard-events
Signed-off-by: Rémi Duraffort <ivoire@videolan.org>

Signed-off-by: Jean-Paul Saman <jean-paul.saman@m2x.nl>

The heap corruption occured when events returned a value. Since the events cross COM boundaries,
the values returned should be allocated in COM context too. Allocating the memory with CoMemTaskAlloc()
should be used instead of new or malloc().

Signed-off-by: Jean-Paul Saman <jean-paul.saman@m2x.nl>

Signed-off-by: Jean-Paul Saman <jean-paul.saman@m2x.nl>

Events that do not originate from within the ActiveX JS context (which is a COM context)
cannot cross into ActiveX/COM context. All events received from libvlc are in a different
thread context then the ActiveX/COM code. Thus from a libvlc event handler callback it is
not possible to call into the ActiveX/COM context.

To solve this issue a seperate thread is created that manages sending of all events for
the ActiveX webplugin (including events from libvlc). All events are by default routed
through the GlobalInterfaceTable (GIT) which takes care ActiveX/COM calls that cross
different thread context in the ActiveX/COM world.
Signed-off-by: Jean-Paul Saman <jean-paul.saman@m2x.nl>