PointerFocus V2.3 Keygen
Jalisa Landgren
Copyright 2008-2011 Kristian Hgsberg
Copyright 2010-2011 Intel Corporation
Copyright 2012-2013 Collabora, Ltd.
Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation files
(the "Software"), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
The above copyright notice and this permission notice (including the
next paragraph) shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
The sync request asks the server to emit the 'done' eventon the returned wl_callback object. Since requests arehandled in-order and events are delivered in-order, this canbe used as a barrier to ensure all previous requests and theresulting events have been handled.
It should be noted that the server side resources consumed inresponse to a get_registry request can only be released when theclient disconnects, not when the client side proxy is destroyed.Therefore, clients should invoke get_registry as infrequently aspossible to avoid wasting memory.
The error event is sent out when a fatal (non-recoverable)error has occurred. The object_id argument is the objectwhere the error occurred, most often in response to a requestto that object. The code identifies the error and is definedby the object interface. As such, each interface defines itsown set of error codes. The message is a brief descriptionof the error, for (debugging) convenience.
This event is used internally by the object ID managementlogic. When a client deletes an object that it had created,the server will send this event to acknowledge that it hasseen the delete request. When the client receives this event,it will know that it can safely reuse the object ID.
The singleton global registry object. The server has a number of global objects that are available to all clients. These objects typically represent an actual object in the server (for example, an input device) or they are singleton objects that provide extension functionality.
When a client creates a registry object, the registry object will emit a global event for each global currently in the registry. Globals come and go as a result of device or monitor hotplugs, reconfiguration or other events, and the registry will send out global and global_remove events to keep the client up to date with the changes. To mark the end of the initial burst of events, the client can use the wl_display.sync request immediately after calling wl_display.get_registry.
The wl_shm_pool object encapsulates a piece of memory shared between the compositor and client. Through the wl_shm_pool object, the client can allocate shared memory wl_buffer objects. All objects created through the same pool share the same underlying mapped memory. Reusing the mapped memory avoids the setup/teardown overhead and is useful when interactively resizing a surface or for many small buffers.
The buffer is created offset bytes into the pool and haswidth and height as specified. The stride argument specifiesthe number of bytes from the beginning of one row to the beginningof the next. The format is the pixel format of the buffer andmust be one of those advertised through the wl_shm.format event.
This request will cause the server to remap the backing memoryfor the pool from the file descriptor passed when the pool wascreated, but using the new size. This request can only beused to make the pool bigger.
This request only changes the amount of bytes that are mmappedby the server and does not touch the file corresponding to thefile descriptor passed at creation time. It is the client'sresponsibility to ensure that the file is at least as big asthe new pool size.
A buffer provides the content for a wl_surface. Buffers are created through factory interfaces such as wl_shm, wp_linux_buffer_params (from the linux-dmabuf protocol extension) or similar. It has a width and a height and can be attached to a wl_surface, but the mechanism by which a client provides and updates the contents is defined by the buffer factory interface.
Color channels are assumed to be electrical rather than optical (in other words, encoded with a transfer function) unless otherwise specified. If the buffer uses a format that has an alpha channel, the alpha channel is assumed to be premultiplied into the electrical color channel values (after transfer function encoding) unless otherwise specified.
If a client receives a release event before the frame callbackrequested in the same wl_surface.commit that attaches thiswl_buffer to a surface, then the client is immediately free toreuse the buffer and its backing storage, and does not need asecond buffer for the next surface content update. Typicallythis is possible, when the compositor maintains a copy of thewl_surface contents, e.g. as a GL texture. This is an importantoptimization for GL(ES) compositors with wl_shm clients.
A wl_data_offer represents a piece of data offered for transfer by another client (the source client). It is used by the copy-and-paste and drag-and-drop mechanisms. The offer describes the different mime types that the data can be converted to and provides the mechanism for transferring the data directly from the source client.
For objects of version 2 or older, this request is used by theclient to give feedback whether the client can receive the givenmime type, or NULL if none is accepted; the feedback does notdetermine whether the drag-and-drop operation succeeds or not.
For objects of version 3 or newer, this request determines thefinal result of the drag-and-drop operation. If the end resultis that no mime types were accepted, the drag-and-drop operationwill be cancelled and the corresponding drag source will receivewl_data_source.cancelled. Clients may still use this event inconjunction with wl_data_source.action for feedback.
To transfer the offered data, the client issues this requestand indicates the mime type it wants to receive. The transferhappens through the passed file descriptor (typically createdwith the pipe system call). The source client writes the datain the mime type representation requested and then closes thefile descriptor.
This request may happen multiple times for different mime types,both before and after wl_data_device.drop. Drag-and-drop destinationclients may preemptively fetch data or examine it more closely todetermine acceptance.
It is a client error to perform other requests thanwl_data_offer.destroy after this one. It is also an error to performthis request after a NULL mime type has been set inwl_data_offer.accept or no action was received throughwl_data_offer.action.
Sets the actions that the destination side client supports forthis operation. This request may trigger the emission ofwl_data_source.action and wl_data_offer.action events if the compositorneeds to change the selected action.
The dnd_actions argument must contain only values expressed in thewl_data_device_manager.dnd_actions enum, and the preferred_actionargument must only contain one of those values set, otherwise itwill result in a protocol error.
While managing an "ask" action, the destination drag-and-drop clientmay perform further wl_data_offer.receive requests, and is expectedto perform one last wl_data_offer.set_actions request with a preferredaction other than "ask" (and optionally wl_data_offer.accept) beforerequesting wl_data_offer.finish, in order to convey the action selectedby the user. If the preferred action is not in thewl_data_offer.source_actions mask, an error will be raised.
This event indicates the actions offered by the data source. Itwill be sent immediately after creating the wl_data_offer object,or anytime the source side changes its offered actions throughwl_data_source.set_actions.
This event will no longer be emitted after wl_data_device.drophappened on the drag-and-drop destination, the client musthonor the last action received, or the last preferred one setthrough wl_data_offer.set_actions when handling an "ask" action.
The most recent action received is always the valid one. Prior toreceiving wl_data_device.drop, the chosen action may change (e.g.due to keyboard modifiers being pressed). At the time of receivingwl_data_device.drop the drag-and-drop destination must honor thelast action received.
Action changes may still happen after wl_data_device.drop,especially on "ask" actions, where the drag-and-drop destinationmay choose another action afterwards. Action changes happeningat this stage are always the result of inter-client negotiation, thecompositor shall no longer be able to induce a different action.
Upon "ask" actions, it is expected that the drag-and-drop destinationmay potentially choose a different action and/or mime type,based on wl_data_offer.source_actions and finally chosen by theuser (e.g. popping up a menu with the available options). Thefinal wl_data_offer.set_actions and wl_data_offer.accept requestsmust happen before the call to wl_data_offer.finish.
The wl_data_source object is the source side of a wl_data_offer. It is created by the source client in a data transfer and provides a way to describe the offered data and a way to respond to requests to transfer the data.
Sets the actions that the source side client supports for thisoperation. This request may trigger wl_data_source.action andwl_data_offer.action events if the compositor needs to change theselected action.
7fc3f7cf58