- User Since
- Dec 2 2013, 11:58 AM (254 w, 1 d)
@Hermet my take on this is that line 175-178 should be removed and replaced with a DBG, and the content (seldata->content.mem) should NEVER ever be printed. It could contain a image or binary data just indicated with a mimetype in the beginning - that is nothing we want to print out on the terminal. (It could contain escape codes or things like this, which could lead to weird behaviour in a terminal emulator.)
Sat, Oct 13
Fri, Oct 12
Thu, Oct 11
@Hermet all this is debugging output, this should actually never been in the function IMO. And errors in return values don't matter at all there. But those are just my two cents :)
eolian_gen is just the binary variable that is used to call eolian_gen in the build process.
The approach yes. However your goal can be achived a lot easier :)
Wed, Oct 10
I never really tried it myself, but its probebly enough to have something like
[binaries] eolian_gen = ['path-to-eolian-gen']
In the cross file.
Looks good to me.
Is the struct in our API or not ?
Tue, Oct 9
... This ... breaks ... eolian_suite ... even CI reported it!
Yes this is not done yet. I just landed the first bunch so it is ready for more, this is deinfintly something that needs to be done - however, i don't have time yet.
Sat, Oct 6
Thu, Oct 4
Okay - but if you aren't happy with the current situation, then things are likely to be changed anyways. With this we have a solution for the constructor things for now. If things change this will get reimplemented in a different way. But in the meantime we have a solution ... :)
funfact of the day:
That is correct thx! :)
Mhmm this appears to not be usefull :(
Wed, Oct 3
THX :) will Land soon, I am not at a laptop right now.
Tue, Oct 2
I actaully don't know right now what this is abount resolving what exactly ?
I will check it once i am back at home on the mac and then merge it :)
Okay, now i understand what you are doing :)
Uuuuhm, how can strlen return a same value of the string does not terminate with /0? O.o
Mon, Oct 1
Fri, Sep 28
Thu, Sep 27
the focus, unfocus legacy events are a bit weird, focus or unfocus usally means that this element has focus, this is the entry point where key events are emitted. However, this is not the case for composition. The focus is on one of the internal elements of the widget, not the composition widget.
In case cd->stack is NULL then top_cd can be NULL I guess ... :) @YOhoho
Tue, Sep 25
Its not perfect yes, but its the meson default, i don't like to change that :)
Seems to be resolved. Cannot be reproduced anymore
Mon, Sep 24
Sun, Sep 23
Fri, Sep 21
Ignore my comment :)
@ManMower it's not really about beeing lazy and not fixing all the cases, it just does not make sense. Where is the difference of you knowing that the callback is already dead, because it was already removed, the object beeing dead, so the callback is never called, or the callback is dead, because it was never registered? Its not that there is some heavy sideeffect if you call callback_del_* twice or so.
Thu, Sep 20
No, I am talking about using "eina_vpath_resolve_snprintf" in line 21, so no free() is required :)
Wed, Sep 19
This Option only works for Android afair :)
Maybe its better to use the vpath resolve variante which takes a static buffer, instead of the allocated string :)
Tue, Sep 18
To me this looks like a problem with the get text call :)
Sep 13 2018
Okay, this is accepted but not landed. I am just yolo'ing it in. On @ManMowers resposibility :)