| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
LayerManager.h included Scene.h
Scene.h included LayerManager.h
LayerManager now just forwards class Scene.
|
|
|
|
|
| |
New messages have been introduced for input handling and client notifications.
These commands have to be reported in the introspect response of Dbus.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Each received messages contains a unique sender handle.
During ServiceConnect call, the application registers it's process id.
this way a mapping of unique client handle to process id is possible.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now 3 different compiler warning presets are used:
- 3rd party libs, unit tests: cmake default compiler settings
- Examples: strict compiler settings to catch many code flaws
- other: very strict compiler settings to detect portability issues
The new build flags allow disabling build of
- LayerManagerService
- ilmClient
- GenericCommunciator
This allows building e.g. only the examples or unit tests
|
|
|
|
| |
On startup LayerManagerService logs the command line it was started with.
|
|
|
|
| |
SIGABRT was not unset.
|
|
|
|
|
|
|
|
|
|
| |
warnings
map::at() function is no available on platforms, while map::operator[] is.
additionally some compiler warnings have been fixed:
- signed/unsigned mismatch
- removed unused variables
|
| |
|
|
|
|
|
| |
these DEBUG_LOG calls generated so much output, that no other information
could be used any more.
|
|
|
|
| |
These issues have occurred using Ubuntu 12.10 pre-release version.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Added support for creating and sending notifications.
Improved handling of incoming message data structure.
removed destroyMessage:
was only used for DBusIpcModule, but lifecycle of received messages
is now handled internally. The external call is not required any more.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Send and Receive have been reimplemented to support asynchronous sending
and receiving of events. This enables the use of DBus signals as transport
for client notifications.
The implementation now features a DBus main loop based on DBusWatches,
select(), DBus filters and dbus_connection_dispatch().
Note: Layer- & SurfaceNotification messages are detected and the DBus
signal handlers are setup as required inside the DbusIpcModule.
removed destroyMessage:
was only used for DBusIpcModule, but lifecycle of received messages
is now handled internally. The external call is not required any more.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated to use new IpcModule API.
Manages internal list of registered notifications. This list is used
to remove notifications on client disconnect.
After processing an incoming command, the list of client notifications
is processed: each notification is created using the IpcModule and
sent to the appropriate list of clients.
removed destroyMessage:
was only used for DBusIpcModule, but lifecycle of received messages
is now handled internally. The external call is not required any more.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds an internal thread thread which implements a receive loop.
The internal thread is required to process any incoming notification event
independent of the current client state.
Inside the client API a list of callbacks is stored to support different
callbacks for different layer and surface notification.
The behavior of the API is unchanged, but additionally asynchronous callbacks
can be supported.
add notification tests:
tests all possible individual notification targets for layers
and surfaces and some combinations aswell.
remove destroyMessage:
was only used for DBusIpcModule, but lifecycle of received messages
is now handled internally. The external call is not required any more.
added thread for notification delivery:
the receive thread used to execute notification callbacks directly,
but this allowed a client to block the receive loop.
Now the receive thread adds all received notifications to a queue.
This queue is processed by the new notification thread, which
triggers the callbacks for incoming notifications.
if a client blocks the notification thread, it will only affect incoming
notifications, but the receive thread will continue working.
If the notification queue is full, the receive thread discards incoming
notifications.
|
|
|
|
|
|
| |
removed destroyMessage:
was only used for DBusIpcModule, but lifecycle of received messages
is now handled internally. The external call is not required any more.
|
|
|
|
|
|
|
| |
changes
Commands that change properties of layers or surfaces now add notifications
to the list of notifications.
|
|
|
|
|
|
| |
The executor now has an interface to add client notifications.
This enables commands to trigger client notifications, if they
have changed a property of a graphical object.
|
|
|
|
|
|
|
|
| |
This feature allows watching all notifications sent for changes
of a layer or surface.
This basically enables monitoring the state changes of a layer or surface.
Additionally the ilmClient init and destroy was improved.
|
|
|
|
|
| |
added API functions for adding and removing notifications
for layers and surfaces.
|
| |
|
| |
|
|
|
|
|
| |
- Removing do while loop in layerSetChromakey
- Removing do while loop in surfaceSetChromakey
|
|
|
|
|
| |
- the shm interfaces has changed in wayland 0.95
- this patch correct the behaviour.
|
|
|
|
|
| |
- set chromakey value for surface and layer
- disable chromakey for surface and layer
|
| |
|
| |
|
|
|
|
|
|
| |
GLESGraphicSystem:
-If chromakey for layer is enabled, creates temporary buffer and render surfaces to it.
-and then the buffer is texturized and composite.
|
|
|
|
|
|
|
|
|
|
|
|
| |
LayerManagerClient:
-Add members into structure of ilmLayerProperties to get status of chromakey by ilm_getPropertiesOfLayer
-ilm_layerSetChromaKey and modification of ilm_getPropertiesOfLayer to get properties of chromakey
GenericCommunicator:
-Add SetLayerChromaKey and GetPropertiesOfLayer
LayerManagerCommands:
-Add LayerSetChromaKeyCommand
|
| |
|
|
|
|
| |
GraphicalObjectTest
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
LayerMangerPlugin
LayerManagerService:
-Add parameter of chromakey to ShaderProgram in order to set chromakey to shaders
X11GLESRenderer:
-renderer_frag_add_uchromakey. If chromakey and fragment color are same, the pixel is ignored.
GLESGraphicSystem:
-If chromakey is enabled, shader for chromakey is enabled.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
LayerManagerClient:
-Add members into structure of ilmSurfaceProperties to get status of chromakey by ilm_getPropertiesOfSurface
-ilm_surfaceSetChromaKey and Modification of ilm_getPropertiesOfSurface to get properties of chromakey
GenericCommunicator:
-Add SetSurfaceChromaKey and GetPropertiesOfSurface
LayerManagerService
-Add colorkey's methods and valiables to GraphicalObject
LayerManagerPlugins
-Add SurfaceSetChromakeyCommand
|
| |
|
|
|
|
|
|
|
| |
destroyMessage() was only called for messages, if typecheck for "Command"
was successful. If type was "Error", destroy was omitted.
This patch changes the behavior to release all received events.
|
|
|
|
|
|
|
|
| |
- This patch will fix a huge memory leak on both client
and generic communicator
- This memory leak will not occur on all ipc module only if dbus is used.
- To guarantee that the ipc message is successfull destroyed
destroyMessage functionality is added.
|