Libavg wiki how to#
Thanks again for your responses & advice.I am trying to figure out how to configure the touch screen for my Samsung ATIV 6. Must admit, it's been good to get the rust off the old cogs even if it was C I learnt with all those years ago.
Libavg wiki code#
I'll check out this how to and binary but in the meantime I've got eclipse & doxygen on my dev system examining the code trying to find the gdksource so I'm still going down multiple roads until I surrender completely or find a working solution. I tried contacting both in the past with no response. I haven't had a chance to check the validity of it yet though.Īlso, in my search I came across this too which while Fedora, it's 18 which has glib new enough to hit the same problem. Plus I just noticed that someone has replied at the bottom with a guide about how to compile it on 14.04 64bit plus a download for the pre-compiled version. Here's the answers page where it's mentioned although the main person in the conversation seems to switch between saying it's 32bit & x86, either way if it's a problem with the newer version of glib surely that issue would be there for both. So I might need some direction of where to be looking for the set for the container. it should be passed on to the default GDK handler.ĭISALLOW_COPY_AND_ASSIGN(MessagePumpGlibX) table to quickly check if a particular event should be handled by us or if We do not want to process all the events ourselves. large enough value (the value of GDK_EVENT_LAST in 2.18.0) so that it works GDK_EVENT_LAST was introduced in GTK+ 2.18.0. was captured and being processed by GDK (when |false|). Indicates whether a GDK event was injected by chrome (when |true|) or if it Gboolean (*gdkdispatcher_)(GSource*, GSourceFunc, void*) when necessary during nested event dispatching. This is stored so that it can be restored TODO(sad): This is currently unused, and may be removed eventually. The list of slave (physical) pointer devices. necessary to query X for the list of devices for each GdkWindow created. processed so that GDK doesn't get to them.
Libavg wiki update#
Update the lookup table and flag the events that should be captured and Static void EventDispatcherX(GdkEvent* event, gpointer data) Virtual bool RunOnce(GMainContext* context, bool block) Use of this source code is governed by a BSD-style license that can beĬlass MessagePumpGlibX : public MessagePumpForUI Copyright (c) 2011 The Chromium Authors. h for the file that's complaining (and where gdksource seems to come from)
cc files.not including the standard includes. This is where I might need some help.as I said I'm trying to fix someone else's code and it's quite large.
Īny help/advice would be greatly appreciated. Considering the amount of files in berkelium alone plus all the libraries it calls I'm finding it hard to work out how to get around the issue.įYI the app I'm trying to get to work is xibo and here's the information the dev has on compiling berkelium. So I suspect it's the version of gcc or glib which have changed their rules or something which means the code got through the compiler but now it's hitting an error and stopping. Gdksource_->source_funcs->dispatch = gdkdispatcher_ įound these references to this type of error. Base/message_pump_glib_x.cc: In member function ‘ virtual bool base::MessagePumpGlibX::RunOnce(GMainContext*, bool)’:īase/message_pump_glib_x.cc:194:44: error: assignment of member ‘_GSourceFuncs::dispatch’ in read-only object
0 kommentar(er)
