more fixes better tests in elm_test

forgot a few files

The widget meanwhile is feature complete, there are tests for the grid position manager and list position manager. The tests for now are only plain copies. Given the complexity of this widget, there will 100% be more bugs to find, and things to clarify, so I would be very happy if people could write examples for that, play with the API, do things that i did not think of. Or simply play around in the tests. Thank you :)

• more tests

add grid position manager and tests

In D9285#171454, @cedric wrote:

On the technical side, I am not sure how I am going to implement the accessor for items as they will be build asynchronously on demand, I wonder how to notify the position manager that they now exist while they didn't before. I am guessing that the best approach for the CollectionView will be to use custom accessor that bind to the data model and the local storage for widget. It seems doable at this point.

well then we could think about another names,
itemBox, itemWidget, itemScroller(?) itemCollection, itemLayout, itemController...
but most of these are also have same problem...

Not to sure of the naming. Efl.Ui.Item_Container seems wrong. What other kind of Efl.Ui.Container would we have that would contain something different? It sounds like a boat for water kind of naming. Not really the most important bit, but that is going to take some time to discuss and find a good name.

Updating after big changes.

Alright this is fixed in upstream meson but it'll probably be a while before the changes are available and I don't really want to be patching meson manually on CI

Another round with some fixes.

more test

Like I said, this should also verify that the sequence of down -> cancel -> up occurs in the expected order and that the event info in down matches the info in cancel.

yey there is a event!!!

Check out D9184, I think this test needs to verify that the 'up' event is also emitted after cancel

This here is a funny one, we are defining the event, but we are not emitting it at all, where or how should we emit this one ? In legacy it seems like we do not have something like this.
Does someone know where or how to emit this ?

According to the mailing thread, this should be merged on the 30.05, if nothing else comes up.

can you update status of this diff?

Thank you :)

I apologize. I've submitted a patch to fix it. 099eb2c315a277bda10f41709d7f936b0ae7fb20

@Jaehyun_Cho Can you *please* *please* *please* be more carefull reviewing these meson changes. The eo files here are just plainly not installed anymore. because line 26 was removed. Additionally, its pure luck that this still works in meson, because you actually pass now a array with a array in array element nr. 0 followed by strings. This is not supported by meson and really only works by luck.

rebase

mesong build support

This is a good point. I've done some testing locally and it doesn't work quite right yet.

Meson build support

When I tried to build with meson, build error happens because efl_gesture_events.eo is dependent on efl_canvas_gesture_xxx.eo

need to check meson build

Code clean up to following comments.

Could you check and remove EINA_UNUSED which are not supposed to be used?

Fix build warning.

Remove Conflict

Code clean up.

Update code to supprt c# binding.