On Wed, 17 Apr 2013 08:17:46 +0200 (CEST)
Jan Engelhardt wrote:
>
> On Wednesday 2012-12-19 09:20, Jan Engelhardt wrote:
> >
> >On Wednesday 2012-12-19 08:27, Pekka Paalanen wrote:
> >>> make[3]: Entering directory
> >>> `/home/abuild/rpmbuild/BUILD/weston-1.0.3/tests' FAIL:
> >>> surface-test.l
Jan Arne Petersen wrote:
I completely agree that editing UTF-8 text as UTF-8 is fine.
I am just wondering if we should have offsets in "Unicode code points"
(with the addition that for invalid byte sequences each byte counts as
one code point) or offsets in bytes.
The reason for the offset in
On 04/16/2013 06:06 PM, Bill Spitzak wrote:
> On 04/16/2013 01:16 AM, Jan Arne Petersen wrote:
>
>> But we still need to think about how to handle invalid byte sequences
>> anyways. What do we expect a toolkit to do when text with invalid byte
>> sequences is inserted with commit_string? How to ha
On Tue, 16 Apr 2013 08:41:16 -0700
Bill Spitzak wrote:
> On 04/15/2013 11:54 PM, Pekka Paalanen wrote:
>
> > Drag & drop obviously has to use pointer focus, so no problem there.
>
> I guess I don't see that. I thought it was very common for the focus to
> remain on the dragged-from application
There seem to be some claims that you cannot random-access a UTF-8
string with errors in it. This is false if you define the handling of
errors to strict patterns that do not contain valid encodings, and
easiest with my recommendation that errors only be 1 byte long.
To make this sample code s
在 2013年4月16日 星期二 10:16:53，Jan Arne Petersen 写道：
> Hi,
>
> On 04/15/2013 09:14 PM, Bill Spitzak wrote:
> > Jan Arne Petersen wrote:
> >> * Changes offsets to be Unicode character instead of byte based
> >
> > No, PLEASE DON'T DO THIS!!!
> >
> > You think you are making things "easier" but you are
On 16 April 2013 04:28, Kristian Høgsberg wrote:
> I'll send out an update tomorrow with plans, ideas and schedule for
> the 1.2 release, but for now I just want to get the 1.1 tarballs out
> there.
In case anyone finds this useful, I've built this for Fedora Rawhide
and as an update to Fedora 19
I've rebased my cms patches from 1.0.6 to master/1.1.0. Two patches
attached. I've been testing them using gnome-color-manager, but you
can equally do something like:
colormgr device-add-profile
/org/freedesktop/ColorManager/devices/weston_drm_0
/org/freedesktop/ColorManager/profiles/icc_4b416c56c
On 04/16/2013 01:16 AM, Jan Arne Petersen wrote:
But we still need to think about how to handle invalid byte sequences
anyways. What do we expect a toolkit to do when text with invalid byte
sequences is inserted with commit_string? How to handle
delete_surrounding_text with the byte offsets not
From: Rob Bradford
The Wayland protocol specifies that the cursor hotspot positions should be
specified as fixed point. Unfortunately weston was prevously accepting those
as integers instead. With this change we accept both but provide a warning if
using the wrong type. For this compatability we
From: Rob Bradford
The Wayland protocol specifies that the values to be passed in for the cursor
hotspot should be fixed point. Unfortunately weston was expecting integers -
since most clients pass the values from the cursor API into the set_cursor
call we can minimize the impact of fixing the bu
On 04/15/2013 11:54 PM, Pekka Paalanen wrote:
Drag & drop obviously has to use pointer focus, so no problem there.
I guess I don't see that. I thought it was very common for the focus to
remain on the dragged-from application, especially when click-to-type is
used. It sounds like you are req
Nice, thanks. Committed. (HTML validated.)
On 04/16, U. Artie Eoff wrote:
> From: "U. Artie Eoff"
>
> The testing.html page briefly describes the current
> Wayland and Weston unit test suites.
>
> Other Wayland enabled test suites/methods will be described
> here, too.
>
> Signed-off-by: U.
From: "U. Artie Eoff"
The testing.html page briefly describes the current
Wayland and Weston unit test suites.
Other Wayland enabled test suites/methods will be described
here, too.
Signed-off-by: U. Artie Eoff
---
index.html | 3 +-
testing.html | 138
Thanks, hopefully they'll review your patch soon since these features are
important on the desktop and since they plan to move Gnome to Wayland by H1
2014 your work should land and get tested in Wayland asap and get
implemented in toolkit(s) upstream in time before 2014.
On Tue, Apr 16, 2013 at 1
2013/4/16 Jiergir Ogoerg
> Hi,
> Between application running on X11 apparently there's no standard way to
> tell if file(s) (their URIs) have been "cut" or "copied" into the
> clipboard, so you don't know what to do on "Paste", so people invented
> (silly) workarounds as explained here [1]:
>
> "
Hi,
On 04/15/2013 09:14 PM, Bill Spitzak wrote:
> Jan Arne Petersen wrote:
>
>> * Changes offsets to be Unicode character instead of byte based
>
> No, PLEASE DON'T DO THIS!!!
>
> You think you are making things "easier" but you are making it much much
> harder.
My main reason was that EFL, IBu
On Mon, 15 Apr 2013 12:32:30 -0700
Bill Spitzak wrote:
> Pekka Vuorela wrote:
>
> >> What I mean is it breaks the api, the api provided by toolkits to
> >> access clipboard will not work at any time, a constraint that
> >> doesn't exist in any other systems.
> >
> > Breaks how? On Qt you get cl
18 matches
Mail list logo
