Hi,
I also have some other questions about "fixed".
As I heard from Mr. Kim, "fixed" just has effect on efficient calculation.
So I though whether a part has fixed value or not, result of its group's
edje_object_size_min_restricted_calc isn't going to be changed.
But I tested a group with just part "A" only, it didn't.
-------------------------------------------------
group { name: "test"; >> the result of edje_object_size_min_restricted_calc,
w=100, h=100.
parts {
part { name: "A";
type: RECT;
description { state: "default" 0.0;
min: 100 100;
max: 100 100;
}
}
}
}
However, when I added "fixed: 1 1;" for "A" part,
edje_object_size_min_restricted_calc for the group returned w=0, h=0.
Could anybody explain this??
Also I tested a group with two parts that one has fixed and the other is not,
and it made me confused.
------------------------------------------------
group { name: "test2"; >> the result of edje_object_size_min_restricted_calc,
w=100, h=100.
parts {
part { name: "A";
type: RECT;
description { state: "default" 0.0;
min: 100 100;
max: 100 100;
fixed: 1 1;
}
}
part { name: "B";
type: RECT;
description { state: "default" 0.0;
rel1 {
to: "A";
relative: 1.0 1.0;
}
}
}
}
}
However when I made part B as comment lines,
edje_object_size_min_restricted_calc for the group returned w=0, h=0.
So does that mean "fixed" not only cares unnecessary calculation but also
affect its group's min size?
------- Original Message -------
Sender : 김승균<sgyun....@samsung.com> S5(책임)/책임/Tizen개발팀(무선)/삼성전자
Date : 2015-11-05 22:16 (GMT+09:00)
Title : [E-devel] How to use "fixed: 1 1" in edc part
Hi~
I have some questions about "fixed" in edc part description.
I understood the main concept of the "fixed" and
edje_object_size_min_restricted_calc logic by irc today.
As I understand, the part needs to add "fixed" in below cases.
a) part's min and max values are same case
------------------------------------------
part {
name: "part_rect";
type: RECT;
description {
state: "default" 0.0;
min: 100 100;
max: 100 100;
fixed: 1 1;
rel1.relative: 0.0 0.0;
rel2.relative: 1.0 1.0;
}
}
------------------------------------------
b) part's rel1 and rel2 has line based relation case
b.1) vertical line relation
------------------------------------------
part {
name: "part_vertcal_line";
type: RECT;
description {
state: "default" 0.0;
min: 100 0;
fixed: 1 0;
rel1.relative: 0.0 0.0;
rel2.relative: 0.0 1.0;
}
}
------------------------------------------
b.2) horizontal line relation
------------------------------------------
part {
name: "part_horizontal_line";
type: RECT;
description {
state: "default" 0.0;
min: 0 100;
fixed: 0 1;
rel1.relative: 0.0 0.0;
rel2.relative: 1.0 0.0;
}
}
------------------------------------------
c) part's rel1 and rel2 has dot based relation case
------------------------------------------
part {
name: "part_horizontal_line";
type: RECT;
description {
state: "default" 0.0;
min: 100 100;
fixed: 1 1;
rel1.relative: 0.0 0.0;
rel2.relative: 0.0 0.0;
}
}
------------------------------------------
edje_object_size_min_restricted_calc API calculates the minimum size of the
part.
and the "fixed" true part can't change its size.
Above case's each part size won't be changed even if the whole edje object
is resized.
So it needs to add "fixed" to reduce unnecessary calculation
of edje_object_size_min_restricted_calc, right?
If then, I think edc compiler or edje loader can add the "fixed" rule
automatically without developer concern.
Or if there are some issue that can't add it automatically, it needs clear
and more easy guide about "fixed" usage for EFL developers :)
Thanks.
_________________________________________________________________
KIM, SEUNG-GYUN
R&D S/W Platform Group SLP Platform Lab. Mobile Communication Division
Telecommunication Network Business SAMSUNG ELECTRONICS CO.,LTD
TEL +82-31-301-4048 Mobile +82-10-7260-4048
E-Mail sgyun....@samsung.com
_________________________________________________________________
[http://www.samsung.net/service/ml/AttachController/201511052216222_BEI0XT4N.gif?cmd=downdirectly&filepath=/LOCAL/ML/CACHE/b/20151109/z5je7euab...@namo.co.kr20151105131321601@sgyun.kimbora1.hwang&contentType=IMAGE/GIF;charset=KSC5601&msgno=681&partno=0.1&foldername=INBOX&msguid=92031]
[SeenTimeChecker?do=7038567541a37f785a12ac4a49cecc2230e8e990e6a8050a41e28bf5
bd706ce42fe50af216eefd44d1b17ce7cdd50431f1bc9e894f4f495bed2705d6268c6898dd8a
aa5ed8b0e8e4326bbdfb2ea96a2fcf878f9a26ce15a0]
------------------------------------------------------------------------------
Presto, an open source distributed SQL query engine for big data, initially
developed by Facebook, enables you to easily query your data on Hadoop in a
more interactive manner. Teradata is also now providing full enterprise
support for Presto. Download a free open source copy now.
http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
