- User Since
- Dec 22 2014, 9:36 PM (423 w, 6 d)
Apr 20 2020
Nov 26 2018
I tried with 1.21.1 and git and I was able to reproduce it with both.
Aug 22 2018
I may I have missed something since then but there had been irc meetings that decided some things and left some other for discussion.
I think it was said that voting was only when there was no consensus.
Now I think it is okay to change things but the most efficient way to do it would be to do another irc meeting.
First take the report of the last irc meeting and rise points that you want to be discussed in the meeting.
Aug 16 2018
@stefan_schmidt yes confirmed, no crash with the patch.
Aug 14 2018
It's a crash so I think this should be a showstopper.
Aug 13 2018
It seems to be ok in 1.21
I get this error on many elementary examples. For example open and close "Box align"
Jul 19 2018
Jul 18 2018
I don't have segfaults but I still have some windows not rendering correctly in some configurations when playing with opengl=full or opengl=es , ELM_ACCEL etc...
I think if other people don't have segfaults we can close this and open a bug about rendering issues.
Jun 6 2018
I don't think this is fixed so reverting the status to open.
Jun 1 2018
@subodh6129 any reason why you closed this?
Apr 18 2018
Apr 14 2018
Like we said on irc, let's make a meeting next weekend if people are up to it.
And let's talk about the possibility of starting a release process too.
Apr 13 2018
It's been one month since the last edit.
I think they are still things undecided here.
Apr 12 2018
Apr 11 2018
Apr 6 2018
Mar 15 2018
@billiob sorry about this, this was a wrong manipulation. (not on purpose)
Mar 14 2018
Mar 10 2018
I just tested the fix.
I had to compile with efl git, I think because of some keywords in edc files.
Does this mean the next version of terminology will only compile with the next version of efl?
I opened a task for the project roadmap : T6768.
Mar 9 2018
Mar 6 2018
Feb 20 2018
Feb 19 2018
I think most people agree that it's too difficult.
Sometimes I think everybody should give up writing themes until the next edje (bob?) / until it becomes easier.
Feb 18 2018
I think if someone strongly wants to make a light theme, they could try to make it.
It might even become the default if it is cool enough...
Feb 14 2018
I assigned it to me, but I am not currently using the python bindings.
Until I do, If someone wants to work on this, feel free to reassign.
I just tried with current git (2018/2/14) and it doesn't seem to be fixed.
Feb 4 2018
Feb 1 2018
I don't understand why you need more input?
Maybe a patch I understand :)
If you think it isn't worth it, maybe change it to wishlist?
How about adding a comment/documentation on object_from_instance, that says something like
"if it returns null, check if an error occured with PyErr_Occured/PyErr_Print (for example)"
Maybe that could help new people.
Jan 29 2018
Oct 22 2017
For me the problem was with the entry_select_allow. (added in 1.19 but I didn't notice it because I jumped from 1.18 to 1.20)
The config entry was introduced with ab68723b60e13ef4b248b24d9a362098eb1a5ccc and then raster added the necessary stuff to update the config.
Oct 18 2017
Sep 24 2017
It doesn't jump anymore but if you click the "0.0 units" entry and press tab it goes to the left arrow.
I think it would be nice if it could go to the next spinner.
Sep 4 2017
I just tried with 1.20.2 and it seems ok. The bug might have been introduced in 1.20.3
Sep 3 2017
I have a way to crash in the same function. (1.20.3)
I just want to add I also have something similar in my application with 1.20.3, will try to reproduce it too.
Mar 23 2017
Ok it works if you specity ELM_ACCEL=none or ELM_ACCEL=gl.
Mar 14 2017
@cedric For me, this bug was not present in 1.18.
Mar 8 2017
Nov 23 2016
This seems to be ok on git.
will close when the next version is released.
Nov 4 2016
I tried with the terminology git version and the problem is also present.
Oct 27 2016
When you press tab, maybe the next focused object also get the press tab event so it focus to the next object?
Oct 26 2016
Jun 17 2016
Feb 6 2016
if you want to always reproduce this you can try the genlist filter example and enter any name from the list.
Jan 25 2016
Jan 21 2016
Nov 18 2015
I just thought this could be on the release announcement, like an unavoidable abi/api change because of a bug. But this kind of bug might be hard to notice.
I think it is difficult for people who makes themes to track changes in the code.
In this situation, it might be nice to have some announcement, like a warning for people who makes themes... no?
Oct 6 2015
The first problem is the same as T1686.
I think we can close this and refer to T1686 and T2704.
In your example, if you set
then the entry gets focused.
if set to false, the item gets the focus. (that is weird)
Oct 3 2015
Sep 26 2015
I'm not sure but maybe it is fine with this patch?
It doesn't emit a x11 clear selection event if it has the same or an older time as the selection.
Sep 25 2015
I will add that the following use case might be common for entries :
There is a bunch of entries, you can edit one, press tab to focus the next one, it is all selected so you don't have to use your mouse or do ctrl-a, just edit it with a new value and go to the next one.
the selection,start signal is called 2 times but maybe that is not a big deal.