On Thu, Nov 27, 2014 at 4:18 AM, Jasper St. Pierre
wrote:
> Hey,
>
> I just built Quickscope from source, and can't find any code that draws
> using cairo inside it. Where is it?
>
i think that quickplot and quickscope are not the same thing.
___
gtk-d
Hey,
I just built Quickscope from source, and can't find any code that draws
using cairo inside it. Where is it?
On Wed, Nov 26, 2014 at 6:08 PM, Lance Arsenault
wrote:
> Hi Emmanuele,
>
> apps using X11 to draw directly should stop doing that, because this is
>> not 1997 any more, and we hav
Hi Emmanuele,
apps using X11 to draw directly should stop doing that, because this is not
1997 any more, and we have better drawing API.
Many many apps need a faster drawing API than Cairo in order to do high
frame rate animations. Interactive games is the most popular example.
I have an
hi;
On 26 November 2014 at 18:40, Lance Arsenault wrote:
> Hello GTK developer,
>
> I've read the latest docs, looked at the latest (git) GTK+3 code, and
> searched the archives, and found not direct answer to this question:
>
> 1. Is there a method, that is not deprecated, that can give the eff
On Wed, Nov 26, 2014 at 10:40 AM, Lance Arsenault wrote:
> Hello GTK developer,
>
> I've read the latest docs, looked at the latest (git) GTK+3 code, and
> searched the archives, and found not direct answer to this question:
>
> 1. Is there a method, that is not deprecated, that can give the eff
Hello GTK developer,
I've read the latest docs, looked at the latest (git) GTK+3 code, and
searched the archives, and found not direct answer to this question:
1. Is there a method, that is not deprecated, that can give the effect
of gtk_widget_set_double_buffered() for GTK3?
There are a l
On Wed, Nov 26, 2014 at 3:31 PM, Emmanuele Bassi wrote:
> hi;
>
> On 26 November 2014 at 14:22, Alexandre Bique
> wrote:
>> On Wed, Nov 26, 2014 at 3:17 PM, Emmanuele Bassi wrote:
>>> you mean apart from the major breakage of API, the massive
>>> complication of the internals, and the portabili
hi;
On 26 November 2014 at 14:22, Alexandre Bique wrote:
> On Wed, Nov 26, 2014 at 3:17 PM, Emmanuele Bassi wrote:
>> you mean apart from the major breakage of API, the massive
>> complication of the internals, and the portability issues?
>
> It is about adding a pointer to a context.
>
> GtkCtx
On Wed, Nov 26, 2014 at 3:17 PM, Emmanuele Bassi wrote:
> you mean apart from the major breakage of API, the massive
> complication of the internals, and the portability issues?
It is about adding a pointer to a context.
GtkCtx *gtk_ctx = gtk_ctx_new();
GtkWindow *window = gtk_window_new();
gtk_
hi;
On 26 November 2014 at 14:15, Alexandre Bique wrote:
> On Wed, Nov 26, 2014 at 3:12 PM, Emmanuele Bassi wrote:
>> if you want to do:
>>
>> Thread 1: gtk_init() → GUI → gtk_main()
>> Thread 2: gtk_init() → GUI → gtk_main()
>> ...
>> Thread N: gtk_init() → GUI → gtk_main()
>>
>> then n
On Wed, Nov 26, 2014 at 3:12 PM, Emmanuele Bassi wrote:
> if you want to do:
>
> Thread 1: gtk_init() → GUI → gtk_main()
> Thread 2: gtk_init() → GUI → gtk_main()
> ...
> Thread N: gtk_init() → GUI → gtk_main()
>
> then no: you cannot achieve that with GTK+, and there are no plans to
> all
hi;
On 26 November 2014 at 14:05, Alexandre Bique wrote:
> On Wed, Nov 26, 2014 at 2:58 PM, Paul Davis
> wrote:
>> this is all part of the many reasons why these toolkits are problematic. Qt
>> has similar issues. The correct answer would depend on the host, which is
>> obviously not a desirab
On Wed, Nov 26, 2014 at 2:58 PM, Paul Davis wrote:
> this is all part of the many reasons why these toolkits are problematic. Qt
> has similar issues. The correct answer would depend on the host, which is
> obviously not a desirable condition to have to understand.
And so what do you think of my
On Wed, Nov 26, 2014 at 2:58 PM, Paul Davis wrote:
> this is all part of the many reasons why these toolkits are problematic. Qt
> has similar issues. The correct answer would depend on the host, which is
> obviously not a desirable condition to have to understand.
So I don't understand. Emmanue
On Wed, Nov 26, 2014 at 3:52 PM, Alexandre Bique
wrote:
>
> So the plugin has to initialize its UI toolkit and render it. But as
> all the plugins are loaded in the same process, for performances
>
reason, it is unsafe to run gtk_main_loop() in each of them.
>
this is all part of the many reason
hi;
On 26 November 2014 at 13:52, Paul Davis wrote:
>> > You can run any number of event loops in a process. You can only run 1
>> > GTK main loop.
>>
>> So can I run one event loop in a thread, do my UI without having a
>> gtk_main_loop?
>
>
> first of all, if the host is written with GTK then
On Wed, Nov 26, 2014 at 2:46 PM, Bernhard Schuster
wrote:
> "VST like plugins" - elaborate please.
>
> I am sure one can handle pretty much anything using g_main_context fun, but
> please provide more information on what you want to achieve exactly.
A VST plugin is a virtual instrument or effect.
On Wed, Nov 26, 2014 at 3:42 PM, Alexandre Bique
wrote:
> On Wed, Nov 26, 2014 at 2:35 PM, Paul Davis
> wrote:
> > You can run any number of event loops in a process. You can only run 1
> GTK main loop.
>
> So can I run one event loop in a thread, do my UI without having a
> gtk_main_loop?
>
fi
"VST like plugins" - elaborate please.
I am sure one can handle pretty much anything using g_main_context fun, but
please provide more information on what you want to achieve exactly.
Best
Bernhard
On Nov 26, 2014 2:42 PM, "Alexandre Bique"
wrote:
> On Wed, Nov 26, 2014 at 2:35 PM, Paul Davis
On Wed, Nov 26, 2014 at 2:35 PM, Paul Davis wrote:
> You can run any number of event loops in a process. You can only run 1 GTK
> main loop.
So can I run one event loop in a thread, do my UI without having a
gtk_main_loop?
On Wed, Nov 26, 2014 at 2:35 PM, Paul Davis wrote:
> On Wed, Nov 26, 20
On Wed, Nov 26, 2014 at 3:16 PM, Alexandre Bique
wrote:
> I need that for implement plugin's UI, like VST plugins.
>
GTK (and all other desktop, non-statically linkable toolkits) are a
particularly poor engineering choice for these types of plugins.
__
On Wed, Nov 26, 2014 at 3:16 PM, Alexandre Bique
wrote:
> Hi,
>
> I wonder if it would be possible to remove gtk's global variables?
> I'd like to do something like:
>
> GtkCtx *gtk_ctx = gtk_init(..);
> GtkWindow *window = gtk_window_new(gtk_ctx, ...);
> ...
> gtk_main_loop(gtk_ctx);
>
> So in t
Hi,
I wonder if it would be possible to remove gtk's global variables?
I'd like to do something like:
GtkCtx *gtk_ctx = gtk_init(..);
GtkWindow *window = gtk_window_new(gtk_ctx, ...);
...
gtk_main_loop(gtk_ctx);
So in this way it would be possible to run many gtk main loop in
different threads b
> The cairo patch is provisional and may need further work; basic problem is
> that a quartz surface created for a window takes its device scale into
> account on the Quartz (CGContext) side but the cairo side doesn't know about
> it and treats it like a 1x-scaled surface. This was leading many
24 matches
Mail list logo
