On Tue, 6 Oct 2009 17:17:10 -0700 Michael Jennings
wrote:
> On Tuesday, 06 October 2009, at 23:43:58 (+0200),
> Kim Woelders wrote:
>
> > In my opinion the MWM hint is not related to EWMH, so I think all
> > that is accomplished is to fetch a potentially rather large atom
> > list which shouldn'
On Tuesday, 06 October 2009, at 23:43:58 (+0200),
Kim Woelders wrote:
> In my opinion the MWM hint is not related to EWMH, so I think all
> that is accomplished is to fetch a potentially rather large atom
> list which shouldn't contain the item being looked for :)
My impression based on the IRC c
On Wednesday, 07 October 2009, at 01:52:47 (+0200),
[email protected] wrote:
> ok, looking through other window managers source setting mwm_hints in
> net_supported is not common. It seems window managers do not announce
> that they handle mwm hints in any special way. I'm going to remove
ok, looking through other window managers source setting mwm_hints in
net_supported is not common. It seems window managers do not announce
that they handle mwm hints in any special way. I'm going to remove my
patch then.. still i think it's would be the correct way to handle it.
There is still th
yes, it says it is 'intended' to replace mwm hints, but
NET_WM_WINDOW_TYPE does not handle the borderless window case.
following EWMH the wm must set hints it supports in _NET_SUPPORTED
(http://standards.freedesktop.org/wm-spec/wm-spec-1.3.html#id2449322).
This way apps can know that mwm hints are
On Tue, 6 Oct 2009, Kim Woelders wrote:
> On Tue, 06 Oct 2009 22:27:38 +0200, Michael Jennings wrote:
>
>> On Tuesday, 06 October 2009, at 21:52:42 (+0200),
>> Kim Woelders wrote:
>>
>>> It seems to me that you are making Eterm e17 compliant in stead of
>>> making
>>> e17 MWM hint compliant.
>>
On Tue, 06 Oct 2009 22:27:38 +0200, Michael Jennings wrote:
> On Tuesday, 06 October 2009, at 21:52:42 (+0200),
> Kim Woelders wrote:
>
>> It seems to me that you are making Eterm e17 compliant in stead of
>> making
>> e17 MWM hint compliant.
>
> I think he did that too. My thought was to make
On Tuesday, 06 October 2009, at 21:52:42 (+0200),
Kim Woelders wrote:
> It seems to me that you are making Eterm e17 compliant in stead of making
> e17 MWM hint compliant.
I think he did that too. My thought was to make Eterm more EWMH
compliant. Do you feel that this patch fails to accomplis
On Tue, 06 Oct 2009 01:54:54 +0200, Enlightenment SVN
wrote:
> Log:
> check wm supporting hints for mwm:
> make borderless also work with window managers that do not pretend to
> be mwm
> Author: jeffdameth
> Date: 2009-10-05 16:54:53 -0700 (Mon, 05 Oct 2009)
> New Revision:
Hi,
I've started getting a strange error when using
evas_object_image_file_set on non-image files. Before evas provided a
load error in case it couldn't load a file. Now anything beyond
evas_object_image_file_set is not run.
## Backtrace
#0 0x00ebd621 in s
Hello.
On Tue, 2009-10-06 at 12:01, Vincent Torri wrote:
>
> The problem is that it is only in automake 1.11. A solution to have it
> anyway would be to add in configure.ac:
>
> m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])])
>
> it should work with and without automake 1.11 and add the
On Tue, Oct 6, 2009 at 7:01 AM, Vincent Torri wrote:
>
> Hey,
>
> automake 1.11 has the nice feature of "silent rule", that it, it can
> remove the compilation command and display only the file that is compiled
> (plus a small character in front of the file (also known as the shaved
> feature).
>
Hey,
automake 1.11 has the nice feature of "silent rule", that it, it can
remove the compilation command and display only the file that is compiled
(plus a small character in front of the file (also known as the shaved
feature).
The problem is that it is only in automake 1.11. A solution to h
13 matches
Mail list logo
