Always the same thing
patch is up to date, cleaner and override previous ones.
--
Sébastien HOUZE
[EMAIL PROTECTED]
--- e/data/themes/default_border.edc 2005-07-13 11:25:22.0 +0200
+++ e.fun/data/themes/default_border.edc 2005-07-18 16:09:44.0 +0200
@@ -213,33 +213,39 @@
Sebastien HOUZE wrote:
Always the same thing
patch is up to date, cleaner and override previous ones.
Some comments.
1. Edit files directly in the e dir, then use cvs diff.
2. Don't remove already existing macros.
3. Split up your patches.
- One to fix the spelling errors.
- One to
Simon TRENY wrote:
Hi Gianpi,
I don't really know where the bug comes from.
Could you try to play your file with emotion_test: emotion_test
/path/to/file.mp3, and tell me if it also crashs.
Thanks for your answer, Simon.
It seems the problem is already in emotion_test... or better to say
Patch concerning top left default theme maximize button :
_ left mouse click : maximize all (vertical horizontal)
_ middle : maximize horizontal
_ right : maximize vertical
Notice : default theme modification.
Many thanks to Sebastian Dransfeld and Dan Sinclair for their precious
advices.
--
Sebastien HOUZE a écrit :
Patch concerning top left default theme maximize button :
_ left mouse click : maximize all (vertical horizontal)
_ middle : maximize horizontal
_ right : maximize vertical
Notice : default theme modification.
Many thanks to Sebastian Dransfeld and Dan Sinclair for
Sebastien HOUZE [EMAIL PROTECTED] [2005-07-19 15:02]:
+#define MAXIMIZE12
+#define MAXIMIZE_H 13
+#define MAXIMIZE_V 14
That's pretty ugly, magic values suck. Where do these come from? What
about putting them in an enumeration? etc ;)
Regards,
Tilman
--
learn to quote:
gianpi wrote:
Thanks for your answer, Simon.
It seems the problem is already in emotion_test... or better to say in
libalsa.
Seems that compiling the latest version of alsalibs fixed the problem.
But now one more issue: when I try to open files, no dialog window shows
up, both with simple open
Hi all. I'm just curious... Why is there an EWL textblock, an
evas_object_textblock, and an ESmart_Textarea? What's the difference
between them? Also, what is (are) the difference(s) between an ESmart
object and an EWL widget? It seems objects made from both (i.e. custom
ESmart object custom EWL
On 7/19/05, Brian Sakal [EMAIL PROTECTED] wrote:
Hi all. I'm just curious... Why is there an EWL textblock, an
evas_object_textblock, and an ESmart_Textarea? What's the difference
between them? Also, what is (are) the difference(s) between an ESmart
object and an EWL widget? It seems objects
Hi all. I'm just curious... Why is there an EWL textblock, an
evas_object_textblock, and an ESmart_Textarea? What's the difference
between them? Also, what is (are) the difference(s) between an ESmart
object and an EWL widget? It seems objects made from both (i.e. custom
ESmart object
Thanks Hisham and Dan. But now my curiosity is further aroused :-).
Since evas_object_textblock is the foundation for the other two, is
there a reason not to fix the bugs/formatting features in that instead
of fixing them in the EWL or ESmart? Are you leaving room for different
ways of formatting?
On Tue, 2005-07-19 at 23:19 -0500, Brian Sakal wrote:
Thanks Hisham and Dan. But now my curiosity is further aroused :-).
Since evas_object_textblock is the foundation for the other two, is
there a reason not to fix the bugs/formatting features in that instead
of fixing them in the EWL or
OK, I'll get to studying the evas_object_textblock code tomorrow. But
one final question: is there anything I should avoid that might
interfere with the code being done for EWL (i.e. if both have triggers,
which will be used, etc.)? Thanks a lot!
On Tue, 2005-07-19 at 23:55 -0500, Brian Sakal wrote:
OK, I'll get to studying the evas_object_textblock code tomorrow. But
one final question: is there anything I should avoid that might
interfere with the code being done for EWL (i.e. if both have triggers,
which will be used, etc.)? Thanks
14 matches
Mail list logo
