Re: [E-devel] Crash using C++ Layout signal API

Andreas Volz <[email protected]>
Newsgroups gmane.comp.window-managers.enlightenment.devel
Message-ID <[email protected]>
Hi Felipe,

great - thanks! :-)

I could confirm the patch works. Hope it gets fast into mainline.

Now I could go forward with porting to the new C++ API.

regards
Andreas

Am 24.06.21 um 15:38 schrieb Felipe Magno de Almeida:
> Hello Andreas,
> 
> I posted a patch, can you see if that fixes your  problem?
> 
> Kind regards,
> 
> On Thu, Jun 24, 2021 at 9:30 AM Andreas Volz <[email protected]> wrote:
>>
>> Hi,
>>
>> just attached the edj and edc file to the phab ticket.
>>
>> regards
>> Andreas
>>
>> Am 24.06.21 um 00:37 schrieb Felipe Magno de Almeida:
>>> Hello Andreas,
>>>
>>> Could you share the glowing.edc file?
>>>
>>> Kind regards,
>>>
>>> On Wed, Jun 23, 2021 at 7:14 PM Felipe Magno de Almeida
>>> <[email protected]> wrote:
>>>>
>>>> Hello Andreas,
>>>>
>>>> This seems weird. It should work, IMO. I'll try to look into this tonight.
>>>>
>>>> Kind regards,
>>>>
>>>> On Wed, Jun 23, 2021 at 6:54 PM Andreas Volz <[email protected]> wrote:
>>>>>
>>>>>
>>>>>
>>>>> Am 23.06.21 um 18:02 schrieb Cedric Bail:
>>>>>>
>>>>>> On Tuesday, June 22nd, 2021 at 11:36 PM, Andreas Volz <[email protected]> wrote:
>>>>>>> Hello together,
>>>>>>>
>>>>>>
>>>>>>> after some waiting time I would like to ask here if some other user
>>>>>>> could at least verify the same crash with C++ API that I described here:
>>>>>>>
>>>>>>
>>>>>>> https://phab.enlightenment.org/T8943
>>>>>>>
>>>>>>
>>>>>>> If I'm not strongly misusing the API than it's a very basic error. Just
>>>>>>> loading an Edje file into a Layout.
>>>>>>
>>>>>> I vaguely remember discussion about this issue. I don't think we actually support function pointer in auto generated code, except for eo callback mechanism, due to some memory lifecycle uncertainty. And it kind of match what your bug report says.
>>>>>>
>>>>>>
>>>>>>> Would be good to know someone else does see the same.
>>>>>>>
>>>>>>
>>>>>>> Do you know a workaround to come around this? Maybe use another C++
>>>>>>> compatible API / mix with C API to continue work on my application?
>>>>>>> regards
>>>>>>
>>>>>> I remember that the workaround would be to switch to use the C API instead of the C++ one as I think we do have a smart pointer trick that allow you to directly use the C pointer and C function from the C++ object.
>>>>>
>>>>> To make it explicit as question. You suggest to not use the C++ API at
>>>>> all in my application or just not for this use case?
>>>>>
>>>>> Is it a good idea to mix usage of C and C++ API as long as it's not
>>>>> fully stable and then adapt later to full C++ usage? Do you know an
>>>>> example how to access the C API object?
>>>>>
>>>>> regards
>>>>> Andreas
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> enlightenment-devel mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>>>>
>>>>
>>>>
>>>> --
>>>> Felipe Magno de Almeida
>>>> Owner @ Expertise Solutions
>>>> www: https://expertise.dev
>>>> phone: +55 48 9 9681.0157
>>>> LinkedIn: in/felipealmeida
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> enlightenment-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> 
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.