From: Brian Mattern <bmattern@ma...> - 2004-01-27 14:00:29
While playing around with eet's in preparation for etcher2, i ran into
a little bit of confusion.
If I load up image data, and then save it back out, it doesn't seem to
As a quick example (http://rephorm.com/files/test.c):
** begin example code **
/* compile with gcc -o test test.c -leet */
* place an edje eet (with at least one image) in the same dir
* run ./test
* eet -d in.eet
* eet -d out.eet
* note that edje_file and edje_file_out are the same size
* note the differnce in size between images/0 images/out
Eet_File *in, *out;
int w, h, a, c, q, l, size;
in = eet_open("in.eet", EET_FILE_MODE_READ);
out = eet_open("out.eet", EET_FILE_MODE_WRITE);
data = eet_data_image_read(in, "images/0", &w, &h, &a, &c, &q, &l);
eet_data_image_write(out, "images/out", data, w, h, a, c, q, l);
data = eet_read(in, "edje_file", &size);
eet_write(out, "edje_file_out", data, size, 1);
** end example code **
in the above code, using eet_read, then eet_write works fine, but
eet_data_image_read, followed by eet_data_image_write doesn't. On my
system, given any edje .eet file as in.eet, i get a 12 byte image/out
file (upon unpacking out.eet). Any Ideas?
Brian Mattern <bmattern@...> [2004-01-27 17:51]:
> While playing around with eet's in preparation for etcher2, i ran into
> a little bit of confusion.
> If I load up image data, and then save it back out, it doesn't seem to
> get saved.
The problem has been solved.
[18:58] <@rephorm> Trill: could you send an email for me to e-devel to ignore
[18:58] * rephorm doesn't have time to get things working right now