Nathan Ingersoll ha scritto:
> On 1/17/07, DaveMDS <[EMAIL PROTECTED]> wrote:
>>
>> evas_object_color_set() don't draw the alpha in the right way:
>> if the color is black the alpha are good,
>> if the color is white the alpha never change until 0 is reached(and then
>> disappear)
>>
>> Seems that
Nathan Ingersoll ha scritto:
On 1/17/07, DaveMDS <[EMAIL PROTECTED]> wrote:
evas_object_color_set() don't draw the alpha in the right way:
if the color is black the alpha are good,
if the color is white the alpha never change until 0 is reached(and then
disappear)
Seems that evas always make t
Hi
attached a patch to add an alpha slider to etk_colorpicker.
If someone need I can also make an option to
disable the slider. (an application could not handle
alpha channel and so could want to hide the slider)
There is a problem in the way the current color is displayed
in the dialog. I have
Zachary Goldberg wrote:
> This further increases Xinerama support with slideshow. Prior to this
> patch occasionally the two "zones" (Monitors) would be come in sync,
> and would have the same background. I believe the cause of this was
> that they slideshows were initialized at the same time, an
On 1/17/07, DaveMDS <[EMAIL PROTECTED]> wrote:
>
> evas_object_color_set() don't draw the alpha in the right way:
> if the color is black the alpha are good,
> if the color is white the alpha never change until 0 is reached(and then
> disappear)
>
> Seems that evas always make the transparency on a
On Wednesday 17 January 2007 18:01, dan sinclair wrote:
> D. Hageman wrote:
> > I guess the real questions that should be asked:
> >
> > a) How many non-standard libaries does one project need to support
> > their project? At what point are there too many?
>
> Define non-standard. None of the efl
On Wednesday 17 January 2007 01:14, Jorge Luis Zapata Muga wrote:
> On 1/17/07, Brian Mattern <[EMAIL PROTECTED]> wrote:
> >
> >
> > The next question is, assuming you guys see it as a viable replacement
> > for ecore_desktop, do we stick this somewhere in libs (as efreet or
> > e_xdg, or whate
On Wed, 17 Jan 2007, DaveMDS wrote:
> dan sinclair ha scritto:
>> Peter Parkanyi wrote:
>>
>> Efreet is more then just menus. It also contains the icon theme code
>> which is used in Ewl. Any other app that want's to use the icons from a
>> given icon theme could use Efreet as well.
>>
>> Along wi
D. Hageman wrote:
>
> I guess the real questions that should be asked:
>
> a) How many non-standard libaries does one project need to support
> their project? At what point are there too many?
>
Define non-standard. None of the efl libraries are 'standards'. We
separate things into librarie
dan sinclair ha scritto:
> Peter Parkanyi wrote:
>
>> On Wednesday 17 January 2007 15:15, you wrote:
>>
>>> On Wednesday 17 January 2007 01:14, Jorge Luis Zapata Muga wrote:
>>>
On 1/17/07, Brian Mattern <[EMAIL PROTECTED]> wrote:
>
>
> The next qu
On 1/17/07, Peter Parkanyi <[EMAIL PROTECTED]> wrote:
>
> I'd argue on that topic. I think it should go to either ecore or e17. The
> reason: I don't think any app but e uses the freedesktop menu, or if they do
> so, they depend on e itself.
That's an incorrect assumption. EWL currently relies on
Peter Parkanyi wrote:
> On Wednesday 17 January 2007 15:15, you wrote:
>
>> On Wednesday 17 January 2007 01:14, Jorge Luis Zapata Muga wrote:
>>
>>> On 1/17/07, Brian Mattern <[EMAIL PROTECTED]> wrote:
>>>
The next question is, assuming you guys see it as a viable
Peter Parkanyi wrote:
> On Wednesday 17 January 2007 15:15, you wrote:
>> On Wednesday 17 January 2007 01:14, Jorge Luis Zapata Muga wrote:
>> > On 1/17/07, Brian Mattern <[EMAIL PROTECTED]> wrote:
>> > >
>> > >
>> > > The next question is, assuming you guys see it as a viable replacement
>> >
On Wednesday 17 January 2007 15:15, you wrote:
> On Wednesday 17 January 2007 01:14, Jorge Luis Zapata Muga wrote:
> > On 1/17/07, Brian Mattern <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > The next question is, assuming you guys see it as a viable replacement
> > > for ecore_desktop, do we sti
14 matches
Mail list logo