Re: [E-devel] [patch] elicit color settings
That standing, it would be an idea to use the common notation as in the rest of the EFL, even if that is technically misleading right? A On Thu, Jan 12, 2006 at 01:03:32PM +0900, Carsten Haitzler wrote: On Thu, 12 Jan 2006 04:17:55 +0100 Morten Nilsen [EMAIL PROTECTED] babbled: dan sinclair wrote: Why is this _argb instead of _rgba? Most of the efl code that I've seen that take colour params take them as r, g, b, a. Might make sense to keep this consistent as I'm sure it will cause a few mistakes. I don't think I've seen #aarrggbb used, isn't it usually #rrggbbaa? that's how ecore_config was when I got there, and I haven't been diddling very much in other places... I can write up a patch to change that, however.. argb is literally how it's stored in memory in terms of a 32bit word with the MSB being A and LSB being B. as with numebrs u write digits from MSN to LSN. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] BUG: configuration panel-background settings-advanced settings
Hi all, I just compiled e17 from cvs. After I started to resetup it, I found one bug. It happens when I try to set up my background using configuaration panel. If I use Advanced Settings, for example, hoose that I want to have a backround for all desktops, and then go back to Default Desktop and press apply, e17 seg faults. Moreover, I realised that e17 seg faults only if Default Desktop option is selected, choosing your desktop background, and this settings are applied. Thanks Aleksej -- Aleksej Struk Master Degree Student Free University of Bozen-Bolzano Faculty of Computer Science phone: +39-0471-061749 cell phone: +39-3204627049 [EMAIL PROTECTED] [EMAIL PROTECTED] - http://www. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] eVolume 0.0.19 buildfix release
Il giorno gio, 12/01/2006 alle 22.37 +0400, Pavel Boldin ha scritto: try version 0.0.20 http://paq.osdn.org.ua/~davinchi/ I tried 0.0.19 and 0.0.20, module compiles well, but the module interface on enlightenment's panel doesn't highlight the Configure button, and the config option on module's pop-up menu tells me that I have no mixers [1]. I've a single soundcard, and every other mixer does work correctly. [1] http://dev.winged.it/gallery/screenshots/evolume_0_0_20_broken_config_dialog -- Ciro Mattia Gonano Winged.it Master - http://www.winged.it FlyingCircus.it member - http://www.flyingcircus.it GPG Keynumber: DEF86925 --- ICQ#: 52631406 signature.asc Description: Questa parte del messaggio è firmata
Re: [E-devel] eVolume 0.0.19 buildfix release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Jan 2006, Pavel Boldin wrote: snip try version 0.0.20 http://paq.osdn.org.ua/~davinchi/ That works, thanks. :) Even the module configuration shows up and works for me. I've updated the Source Mage GNU/Linux package to 0.0.20. Thanks! - -sandalle - -- Eric Sandall | Source Mage GNU/Linux Developer [EMAIL PROTECTED] | http://www.sourcemage.org/ http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU http://counter.li.org/ #196285 | http://www.shock.wsu.edu/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDxu6YHXt9dKjv3WERAk6JAJ0eB8WK9NYeCvY0lM2Khf0lPthi2ACcCxba OocEwmdBXMIsvivnjy/wtZc= =Lp7+ -END PGP SIGNATURE- --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] eVolume 0.0.19 buildfix release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Jan 2006, Hawkwind Cliff Wade wrote: I've just tested 0.20 and got the same No Mixer problem. I've got a freshly updated E as of very late last night and restarting E doesn't help either. It compiles and loads without any problems, but nothing can be configured. snip Did you remove the prior configuration for evolume? You can find these with: $ find $HOME | grep -i evolume CC'ing e-devel list. - -sandalle - -- Eric Sandall | Source Mage GNU/Linux Developer [EMAIL PROTECTED] | http://www.sourcemage.org/ http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU http://counter.li.org/ #196285 | http://www.shock.wsu.edu/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDxvkEHXt9dKjv3WERAsYHAJ9jXZqbeR+2gEQlMLlQQT5s74Uf3ACgsMWY qWVdw6QZ7W6ag8B/oGG8MVo= =NLnr -END PGP SIGNATURE- --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] eVolume 0.0.19 buildfix release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 12 Jan 2006, Hawkwind Cliff Wade wrote: I didn't have any prior to this build, as I always check. snip Please keep this on list, I am not an e17 developer, just a user. - -sandalle - -- Eric Sandall | Source Mage GNU/Linux Developer [EMAIL PROTECTED] | http://www.sourcemage.org/ http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU http://counter.li.org/ #196285 | http://www.shock.wsu.edu/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDxwDfHXt9dKjv3WERAg+0AJ0WVw496ZJREeR46RA4mKR1YNFuSQCeN3k8 WhiOFVzIsTtBf1bss58IzhY= =b1DK -END PGP SIGNATURE- --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] ecore_exe event type consistancy.
On Sat, 7 Jan 2006 02:50:03 +1000 David Seikel [EMAIL PROTECTED] wrote: On Sat, 7 Jan 2006 00:35:42 +0900 Carsten Haitzler (The Rasterman) [EMAIL PROTECTED] wrote: i would argue that ECORE_EVENT_EXE is fine as its a CORE ecore event (not a sub ecore system like ecore_con)... ? I'm thinking consistency in naming things IPC related. I think that merging fork'n'pipe with ecore_ipc might be good, it's just another IPC method, why should it be different? Most of the ways of dealing with it from the ecore users perspective are mostly similar. Most of the differences are simply due to current inconsistent naming and lack of an exe add event. The user doesn't see any core ecore / sub ecore issues, it's all ecore_*_whatever to them. As I said before, the naming of the exit event is historical, and I'm prepared to wear that. The data event is new though, and should be consistent with other IPC data events. It's semantics are the same, hell most of the code was just cut'n'paste from ecore_con. I've thought about it some more, and the fact that the ecore_exe functions are all called ecore_exe_* like the sub ecore functions means that I consider it to be more consistent. The style guide says to use name spaced, object oriented style names, so ecore_exe_* and ECORE_EXE_* has to be the way to go. I'll make these changes, but keep ECORE_EVENT_EXE_EXIT around for historical reasons (so no one can blame me for beaking evidence). pgphCBYmwgpSL.pgp Description: PGP signature
Re: [E-devel] ecore_exe event type consistancy.
On Fri, 13 Jan 2006 12:04:19 +1000 David Seikel [EMAIL PROTECTED] babbled: On Sat, 7 Jan 2006 02:50:03 +1000 David Seikel [EMAIL PROTECTED] wrote: On Sat, 7 Jan 2006 00:35:42 +0900 Carsten Haitzler (The Rasterman) [EMAIL PROTECTED] wrote: i would argue that ECORE_EVENT_EXE is fine as its a CORE ecore event (not a sub ecore system like ecore_con)... ? I'm thinking consistency in naming things IPC related. I think that merging fork'n'pipe with ecore_ipc might be good, it's just another IPC method, why should it be different? Most of the ways of dealing with it from the ecore users perspective are mostly similar. Most of the differences are simply due to current inconsistent naming and lack of an exe add event. The user doesn't see any core ecore / sub ecore issues, it's all ecore_*_whatever to them. As I said before, the naming of the exit event is historical, and I'm prepared to wear that. The data event is new though, and should be consistent with other IPC data events. It's semantics are the same, hell most of the code was just cut'n'paste from ecore_con. I've thought about it some more, and the fact that the ecore_exe functions are all called ecore_exe_* like the sub ecore functions means that I consider it to be more consistent. The style guide says to use name spaced, object oriented style names, so ecore_exe_* and ECORE_EXE_* has to be the way to go. I'll make these changes, but keep ECORE_EVENT_EXE_EXIT around for historical reasons (so no one can blame me for beaking evidence). ok - though it depends how u look at the object ECORE_EVENT_* indicates it belongs to ecore, is of a type events.. then sub type something else... it just is a matter of which object is priority... -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Imlib not working under xorg-6.9?
On Fri, 13 Jan 2006 01:54:26 + (GMT) chinlu chinawa [EMAIL PROTECTED] babbled: Hi, I've ported xwindows from xfree4.4 towards to xorg-6.9, and seems to be working properly. I did actually remove /usr/X11R6 and /etc/X11, so this is a fresh new server's installation. The funny thing is that after this, imlib is no longer working on my computer. I've recompiled it, and it did it nicely, but when I try to execute again the example program, the Xlib version found in here: http://www.enlightenment.org/Libraries/Imlib/index.html It still doesn't show any images at all, as I've been trying with different formats. I've kept X loading same modules, and tried as well getting rid of those not actually found on my previous xfree server configuration, such as xcomposite. Is this a bug? Kind Regards, errr. use imlib2 or Evas or something more modern... :) -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] ecore_exe event type consistancy.
On Thu, 12 Jan 2006 21:31:03 -0500 dan sinclair [EMAIL PROTECTED] wrote: David Seikel wrote: On Sat, 7 Jan 2006 02:50:03 +1000 David Seikel [EMAIL PROTECTED] wrote: I'll make these changes, but keep ECORE_EVENT_EXE_EXIT around for historical reasons (so no one can blame me for beaking evidence). Um, we haven't even had a release yet. Do we want to start carrying around depreciated apis? You are correct. I just did a cvs update, autogen.sh, and make in my evidence directory. There was no updates from cvs, and it failed to compile. Thus I will no longer consider it important to avoid breaking it. This will be just one more thing to fix if anybody decides to update evidence. pgp7p1l4mrXlt.pgp Description: PGP signature
