search for: handleev

...rd should be set out for the naming of events like this. -------------- next part -------------- diff --git a/include/compiz.h b/include/compiz.h index 61a9de5..a7eff50 100644 --- a/include/compiz.h +++ b/include/compiz.h @@ -568,6 +568,12 @@ typedef void (*FiniPluginForDisplayProc) typedef void (*HandleEventProc) (CompDisplay *display, XEvent *event); +typedef void (*HandleCompizEventProc) (CompDisplay *display, + char *pluginName, + char *eventName, + CompOption *option, + int nOption); + typedef Bool (*CallBackProc) (vo...

...urther clicks can come from. That's the nuisance part. The second problem is that the device may try to plot() into a non-existant window. Assume that the window was destroyed by some other part of the program. The device (at some point in the future) will receive a DestroyNotify event that handleEvent ignores. Blissfully! *No KillDevice is called* when the window is destroyed by something other than the WM_DELETE_WINDOW mechanism! This happens when you embed the X11 device into another window/application. For starters, the device no longer receives WM_DELETE_WINDOW client messages. But it...

...If we need some user data attached to actions then that should go into the CompAction struct but I'm not sure we want that at all. If you want to create run-time actions like your compiz-schema code is doing I suggest that you just use addScreenAction and check for a matching event manually in handleEvent. btw, when you're making changes to compiz.h, please make sure that they are indented correctly and matching coding style is used. - David

...right from R. However, the x11-window does not respond to any events. E.g. clicking the close-button simply does not close the window and the contents in the window do not get refreshed when it was hidden by other windows. I figured that the reason for this might be, that R_ProcessEvents () and handleEvent () in devX11.c do not get called (of course I might be completely wrong?). So I tried calling R_ProcessEvents () manually, but I can't get that to link (unresolved symbol R_ProcessEvents). Any hints on how I can get this to work? Thanks Thomas

..._trap_eval () #19 0x000de7e6 in rb_thread_trap_eval () #20 0x000da18c in rb_eval_string_wrap () #21 0x000dad6a in rb_eval_string_wrap () #22 0x000db7ed in rb_respond_to () #23 0x000db8d6 in rb_funcall () #24 0x010ab236 in wxRbCallback::EventThunker () at string.h:690 #25 0x0139fbc3 in wxAppConsole::HandleEvent (this=0x3ad2d0, handler=0x833200, func={__pfn = 0x10ab18c <wxRbCallback::EventThunker(wxEvent&)>, __delta = 0}, event=@0xbfffdf24) at ../src/common/appbase.cpp:320 #26 0x0143ba6e in wxEvtHandler::ProcessEventIfMatches (entry=@0x1582a500, handler=0x833200, event=@0xbfffdf24) at ../src/c...

...URL to JSON file + * @param {Function} callback Callback function + */ + function loadScript(src, callback) { + var script = document.createElement(''script''); + script.type = ''text/javascript''; + script.src = src; + if (callback) { + var evl = {}; + evl.handleEvent = function(e) { + callback(); + }; + script.addEventListener(''load'' ,evl ,true); + } + document.getElementsByTagName(''head'')[0].appendChild(script); + return; + }; + + /** * Calls the API specific implementation of a particular method. */...

...h trial and error, I decided to put a breakpoint in the removeDevice function from device.c. I then do what I describe above, and get the following backtrace from gdb, edited to show what I think is going on. (gdb) bt #0 removeDevice (devNum=1, findNext=TRUE) at devices.c:307 #1 0xb7962855 in handleEvent (event= {type = 33, xany = {type = 33, serial = 15621, send_event = 1, ...(snip)... , 268686226}}) at devX11.c:627 #2 0xb796296c in R_ProcessX11Events (data=0x0) at devX11.c:665 #3 0x080fd99c in R_runHandlers (handlers=0x8263d28, readMask=0x82cf6a0) at sys-std.c:363 #4 0xb74e15...

...ng to add a generic action notification which plugins can wrap to see when other actions are initiated and terminated. Some plugins like 3D 'react' to the cube being rotated manually but not when keyboard initiated. I came to the conclusion that the best place for it to go would be in the handleEvent function. If the trigger*Binding function returns true then it should send the notification, but this does not return true even if the action initiated because they are returning false. Is there is reason for this? If so can you explain exactly what returning true/false means. Regards Mike

...rovider.java:300) at org.eclipse.ui.internal.services.WorkbenchSourceProvider.handleCheck(WorkbenchSourceProvider.java:286) at org.eclipse.ui.internal.services.WorkbenchSourceProvider.checkOtherSources(WorkbenchSourceProvider.java:855) at org.eclipse.ui.internal.services.WorkbenchSourceProvider$6.handleEvent(WorkbenchSourceProvider.java:839) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1262) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at...

...GenericTreeCtrl::PaintLevel(wxGenericTreeItem*, wxDC&, int, int&) () #6 0x03389138 in wxGenericTreeCtrl::OnPaint(wxPaintEvent&) () #7 0x0325eaf8 in wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) () #8 0x0325e27c in wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) () #9 0x0325eca4 in wxEvtHandler::ProcessEvent(wxEvent&) () #10 0x0325ecd0 in wxEvtHandler::ProcessEvent(wxEvent&) () #11 0x03324ab8 in wxScrollHelperEvtHandler::ProcessEvent(wxEvent&) () #12 0x03290578 in wxWindow::MacDoRedraw(void*, long) () #13 0x0328...

...Bool dirtyPluginList; @@ -1107,6 +1110,16 @@ findCursorAtDisplay (CompDisplay *display); /* event.c */ +typedef struct _CompDelayedEdgeSettings +{ + CompDisplay *d; + + unsigned int edge; + unsigned int state; + + CompOption option[7]; +} CompDelayedEdgeSettings; + void handleEvent (CompDisplay *display, XEvent *event); diff --git a/metadata/core.xml.in b/metadata/core.xml.in index 8424ab1..64d418a 100644 --- a/metadata/core.xml.in +++ b/metadata/core.xml.in @@ -44,6 +44,13 @@ <min>0</min> <max>10000</max> </option> +...

...fault with the following backtrace: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000005 0x906fc265 in CFGetTypeID () (gdb) whe whe #0 0x906fc265 in CFGetTypeID () #1 0x92fc6246 in HIAboutBox () #2 0x92e3860e in HIStdAppHandler::HandleEvent () #3 0x92e358fe in TEventHandler::EventHandler () #4 0x92daf863 in DispatchEventToHandlers () #5 0x92daec9d in SendEventToEventTargetInternal () #6 0x92dcb08e in SendEventToEventTarget () #7 0x92dffc9d in SendHICommandEvent () #8 0x92e26377 in SendMenuCommandWithContextAndModifiers () #9...

...Asterisk::Manager::eventcallback('Asterisk::Manager=HASH(0x8776868)','Ev ent','Hangup','Uniq ueid',1109334287.3,'Channel','OH323/L19615','Cause',0,...) called at /usr/lib/perl5/site_perl/5.8.0 /Asterisk/Manager.pm line 331 Asterisk::Manager::handleevent('Asterisk::Manager=HASH(0x8776868)') called at /usr/lib/perl 5/site_perl/5.8.0/Asterisk/Manager.pm line 323 Asterisk::Manager::eventloop('Asterisk::Manager=HASH(0x8776868)') called at ./ast-rad-acc.p l line 113 eval {...} called at ./ast-rad-acc.pl line 113 ... Althoug...

FYI, I have put up a forum post [1] where I am going to maintain information about the netwm api for the dbus plugin. I have gone through the EWMH spec [2] and broken it down into a dbus compatible api, it seems to be good and roughly compatible with the existing compiz one. I think everything should be self explanitory, if there are any comments or if there is anything I have misunderstood or

...nown Source) at sun.awt.SunGraphicsCallback.runOneComponent(Unknown Source) at sun.awt.SunGraphicsCallback.runComponents(Unknown Source) at java.awt.Container.paint(Unknown Source) at sun.awt.RepaintArea.paint(Unknown Source) at sun.awt.windows.WComponentPeer.handleEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue....

...ager.java:349) at org.eclipse.ui.internal.ViewPane.updateActionBars(ViewPane.java:449) at org.eclipse.ui.internal.ViewActionBars.updateActionBars(ViewActionBars.java:59) at org.eclipse.ui.SubActionBars.updateActionBars(SubActionBars.java:610) at de.walware.statet.nico.ui.console.NIConsolePage$6.handleEvent(NIConsolePage.java:599) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1182) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1163) at org.eclips...

...mind this limitation too much but I would like to hear if I am doing something wrong. -------------- next part -------------- diff --git a/include/compiz.h b/include/compiz.h index 61a9de5..f3c6e6c 100644 --- a/include/compiz.h +++ b/include/compiz.h @@ -751,6 +751,8 @@ struct _CompDisplay { HandleEventProc handleEvent; + unsigned int mouseOnEdge; + CompPrivate *privates; }; -------------- next part -------------- diff --git a/src/event.c b/src/event.c index 2d182be..b228dde 100644 --- a/src/event.c +++ b/src/event.c @@ -266,12 +266,18 @@ triggerButtonPressBindings (CompDisplay...

...eans that X11DeviceDriver() cannot do anything that potentially accesses the dd structure because it isn't there yet, and the things it cannot do apparently includes calling R_ProcessX11Events(). [To be completely sure that this is actually still true, I'd need to have a closer look at what handleEvent() does.] > > So to fix things, it would seem that you could (a) add the device before attempting to start the driver, preparing to back it out if the driver fails to start, or (b) add a call to R_ProcessX11Events() _after_ the GEaddDevice2(dd, devname). Option (b) is probably the easiest....

...tHandler::ProcessEvent () from lib/wxruby2.so #59 0xb7ad3730 in wxGenericTreeCtrl::DoSelectItem () from lib/wxruby2.so #60 0xb7ad442f in wxGenericTreeCtrl::OnMouse () from lib/wxruby2.so #61 0xb7b5b9be in wxEvtHandler::ProcessEventIfMatches () from lib/wxruby2.so #62 0xb7b5c033 in wxEventHashTable::HandleEvent () from lib/wxruby2.so #63 0xb7b5c414 in wxEvtHandler::ProcessEvent () from lib/wxruby2.so #64 0xb7a01400 in gtk_window_button_press_callback () from lib/wxruby2.so #65 0xb7035b00 in _gtk_marshal_BOOLEAN__BOXED () from /usr/lib/libgtk-x11-2.0.so.0 #66 0xb6cb479b in g_closure_invoke () from /u...

...eans that X11DeviceDriver() cannot do anything that potentially accesses the dd structure because it isn't there yet, and the things it cannot do apparently includes calling R_ProcessX11Events(). [To be completely sure that this is actually still true, I'd need to have a closer look at what handleEvent() does.] >>> So to fix things, it would seem that you could (a) add the device before attempting to start the driver, preparing to back it out if the driver fails to start, or (b) add a call to R_ProcessX11Events() _after_ the GEaddDevice2(dd, devname). Option (b) is probably the easies...