Tizen Developers

Hi,

can you please explain more about your issue, do you use the sample code to create your app, share the code where you call your gl_content_get_cb will be help to found the issue.

thanks.

f.y.i.

For the default style,  each item have three part [elm.swallow.icon, elm.text, elm.swallow.end], the swallow part will call the content_get, the text part will call the text_get. So, I think it's right to call content_get twice for each item.

For the full style, each item only have one part [elm.swallow.content], I think in this case the content_get only get called once for each item.

Could you try to check the part name in the content_get function, such as dlog it to console to check the difference. 

Hi,

For the IDE help ducument there is a exaplain for func in Elm_Genlist_Item_Class:

The func structure contains pointers to functions that are called when an item is going to be created or deleted. All of them receive a data parameter that points to the same data passed to the elm_genlist_item_append() and related item creation functions, and an obj parameter that points to the genlist object itself.

I have try the full mode and and the content_get was called twice, but acutally in my code only has 1 time operation(elm_genlist_item_append) which related to item create /deleted, seems this is design like this.

For more, I checked the sample code in IDE:

In genlist demo, function gl_content_get_cb, there is one line strange code I list below, seems they know the content get will called twice.

if (rand() % 2) return NULL;

content_get will be called every time the genlist needs the content. content objects returned may be deleted by genlist at any point. in the case of large lists, content_get will be called for lots of non-visible items because genlist is attempting to calulate sizing of tiems based on their content (width of the list so it may have to scroll horizontally, and every item could have a different height based on content). so this is one path you will get more than one call over the lifetime of an item in a gnelist.

as you scroll through the list, as needed, items will call the content_get to get the actual content for the swallow parts.

in addition the content_get is called PER swallow part in the item. the const char *part string param will name the part it is asking for. return different content per part as desired (or NULL for no content at all).

this is the "contract" between you and genlist. if you want to be really fast - make sure you are fast in returning new content objects. don't, for example, go do some sqlite or file i/o query to figure out what to return - ensure results are already in memory. if they are not, this is your opportunity to queue a thread worker to go do the "slow fetch i/o" and WHEN that worker is done, call an update on this item, which will force a call on content_get again and now you can return data that is now cached/stored in ram.

i hope this helps.

Could be for adapting or once PER swallow part - eg standard genlist item class has 2 swallow areas - the one at the start and another at the end of the item. soit'll be called once per swallow with the string passed in as above named differently so you know which part it wants.