Re: [E-devel] A Problem about using non-smart objects in Elemenetary.
On Thu, 28 Jul 2011 10:17:57 +0900 ChunEon Parkher...@naver.com said: i say remove the smart object check from smart_data_get as its not that useful and helps a lot here. Ok. I see.. But even it's the simple way we can do, I still wonder that the MAGIC CHECK is not strange in smart_data_get function since it is just checking whether object is smart or not... Do anybody has any other opinion ? If many agree with raster (or nobody reply to this mail), then i will apply the changes. Thank you. Let's run together for the best moment! -Regards, Hermet- -Original Message- From: Carsten Haitzlerlt;ras...@rasterman.comgt; To: ChunEon Parklt;her...@naver.comgt; Cc: EFLlt;enlightenment-devel@lists.sourceforge.netgt; Sent: 11-07-27(μ) 18:16:55 Subject: Re: [E-devel] A Problem about using non-smart objects in Elemenetary.On Mon, 11 Jul 2011 13:04:38 +0900 ChunEon Parklt;her...@naver.comgt; said: we also have the elm error abort stuff too. but as such i think some calls in evas can be made to not barf if its not a smart object, like getting smart data. if its not a smart obj just safely return null - thats basically then a simple way to detect if its a smart object or not. thats the right thing to do. Hello, EFL developers. I just have one question and need your opinions. In many cases, many non-smart objects are used in elementary e.g) evas_object_rectangle. Those objects are passed to elm_widget APIs frequently which calls the smart_object_data_get in API_ENTRY define. Since those are not smart objects, they will be handled by MAGIC_CHECK(EVAS_OBJ_SMART) in evas. If EVAS_DEBUG_ABORT is enabled, in that case the program will be aborted. Consequently, elementary can't use the EVAS_DEBUG_ABORT property usefully now as you can check it with elementary_test So, my question is where do we fix this problem ? 1. Find all the non-smart objects in elementary then change to smart objects? 2. Or before call the smart_object_data_get in API_ENTRY, check the object_type then pass the API call if the objects are non-smart? 3. Or skip the smart object MAGIC_CHECK in Evas? 4. Or leave them and don't use EVAS_DEBUG_ABORT? What do you think about this? -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler) ras...@rasterman.com -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] A Problem about using non-smart objects in Elemenetary.
removed! Let's run together for the best moment! -Regards, Hermet- -Original Message- From: Carsten Haitzlerlt;ras...@rasterman.comgt; To: ChunEon Parklt;her...@naver.comgt; Cc: EFLlt;enlightenment-devel@lists.sourceforge.netgt; Sent: 11-07-29(κΈ) 20:19:01 Subject: Re: [E-devel] A Problem about using non-smart objects in Elemenetary.On Thu, 28 Jul 2011 10:17:57 +0900 ChunEon Parklt;her...@naver.comgt; said: i say remove the smart object check from smart_data_get as its not that useful and helps a lot here. Ok. I see.. But even it's the simple way we can do, I still wonder that the MAGIC CHECK is not strange in smart_data_get function since it is just checking whether object is smart or not... Do anybody has any other opinion ? If many agree with raster (or nobody reply to this mail), then i will apply the changes. Thank you. Let's run together for the best moment! -Regards, Hermet- -Original Message- From: Carsten Haitzlerlt;ras...@rasterman.comgt; To: ChunEon Parklt;her...@naver.comgt; Cc: EFLlt;enlightenment-devel@lists.sourceforge.netgt; Sent: 11-07-27(μ) 18:16:55 Subject: Re: [E-devel] A Problem about using non-smart objects in Elemenetary.On Mon, 11 Jul 2011 13:04:38 +0900 ChunEon Parklt;her...@naver.comgt; said: we also have the elm error abort stuff too. but as such i think some calls in evas can be made to not barf if its not a smart object, like getting smart data. if its not a smart obj just safely return null - thats basically then a simple way to detect if its a smart object or not. thats the right thing to do. Hello, EFL developers. I just have one question and need your opinions. In many cases, many non-smart objects are used in elementary e.g) evas_object_rectangle. Those objects are passed to elm_widget APIs frequently which calls the smart_object_data_get in API_ENTRY define. Since those are not smart objects, they will be handled by MAGIC_CHECK(EVAS_OBJ_SMART) in evas. If EVAS_DEBUG_ABORT is enabled, in that case the program will be aborted. Consequently, elementary can't use the EVAS_DEBUG_ABORT property usefully now as you can check it with elementary_test So, my question is where do we fix this problem ? 1. Find all the non-smart objects in elementary then change to smart objects? 2. Or before call the smart_object_data_get in API_ENTRY, check the object_type then pass the API call if the objects are non-smart? 3. Or skip the smart object MAGIC_CHECK in Evas? 4. Or leave them and don't use EVAS_DEBUG_ABORT? What do you think about this? -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler) ras...@rasterman.com -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler) ras...@rasterman.com -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] A Problem about using non-smart objects in Elemenetary.
On Mon, 11 Jul 2011 13:04:38 +0900 ChunEon Parkher...@naver.com said: we also have the elm error abort stuff too. but as such i think some calls in evas can be made to not barf if its not a smart object, like getting smart data. if its not a smart obj just safely return null - thats basically then a simple way to detect if its a smart object or not. thats the right thing to do. Hello, EFL developers. I just have one question and need your opinions. In many cases, many non-smart objects are used in elementary e.g) evas_object_rectangle. Those objects are passed to elm_widget APIs frequently which calls the smart_object_data_get in API_ENTRY define. Since those are not smart objects, they will be handled by MAGIC_CHECK(EVAS_OBJ_SMART) in evas. If EVAS_DEBUG_ABORT is enabled, in that case the program will be aborted. Consequently, elementary can't use the EVAS_DEBUG_ABORT property usefully now as you can check it with elementary_test So, my question is where do we fix this problem ? 1. Find all the non-smart objects in elementary then change to smart objects? 2. Or before call the smart_object_data_get in API_ENTRY, check the object_type then pass the API call if the objects are non-smart? 3. Or skip the smart object MAGIC_CHECK in Evas? 4. Or leave them and don't use EVAS_DEBUG_ABORT? What do you think about this? -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] A Problem about using non-smart objects in Elemenetary.
Ok. I see.. But even it's the simple way we can do, I still wonder that the MAGIC CHECK is not strange in smart_data_get function since it is just checking whether object is smart or not... Do anybody has any other opinion ? If many agree with raster (or nobody reply to this mail), then i will apply the changes. Thank you. Let's run together for the best moment! -Regards, Hermet- -Original Message- From: Carsten Haitzlerlt;ras...@rasterman.comgt; To: ChunEon Parklt;her...@naver.comgt; Cc: EFLlt;enlightenment-devel@lists.sourceforge.netgt; Sent: 11-07-27(μ) 18:16:55 Subject: Re: [E-devel] A Problem about using non-smart objects in Elemenetary.On Mon, 11 Jul 2011 13:04:38 +0900 ChunEon Parklt;her...@naver.comgt; said: we also have the elm error abort stuff too. but as such i think some calls in evas can be made to not barf if its not a smart object, like getting smart data. if its not a smart obj just safely return null - thats basically then a simple way to detect if its a smart object or not. thats the right thing to do. Hello, EFL developers. I just have one question and need your opinions. In many cases, many non-smart objects are used in elementary e.g) evas_object_rectangle. Those objects are passed to elm_widget APIs frequently which calls the smart_object_data_get in API_ENTRY define. Since those are not smart objects, they will be handled by MAGIC_CHECK(EVAS_OBJ_SMART) in evas. If EVAS_DEBUG_ABORT is enabled, in that case the program will be aborted. Consequently, elementary can't use the EVAS_DEBUG_ABORT property usefully now as you can check it with elementary_test So, my question is where do we fix this problem ? 1. Find all the non-smart objects in elementary then change to smart objects? 2. Or before call the smart_object_data_get in API_ENTRY, check the object_type then pass the API call if the objects are non-smart? 3. Or skip the smart object MAGIC_CHECK in Evas? 4. Or leave them and don't use EVAS_DEBUG_ABORT? What do you think about this? -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler) ras...@rasterman.com -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] A Problem about using non-smart objects in Elemenetary.
Hello, EFL developers. I just have one question and need your opinions. In many cases, many non-smart objects are used in elementary e.g) evas_object_rectangle. Those objects are passed to elm_widget APIs frequently which calls the smart_object_data_get in API_ENTRY define. Since those are not smart objects, they will be handled by MAGIC_CHECK(EVAS_OBJ_SMART) in evas. If EVAS_DEBUG_ABORT is enabled, in that case the program will be aborted. Consequently, elementary can't use the EVAS_DEBUG_ABORT property usefully now as you can check it with elementary_test So, my question is where do we fix this problem ? 1. Find all the non-smart objects in elementary then change to smart objects? 2. Or before call the smart_object_data_get in API_ENTRY, check the object_type then pass the API call if the objects are non-smart? 3. Or skip the smart object MAGIC_CHECK in Evas? 4. Or leave them and don't use EVAS_DEBUG_ABORT? What do you think about this? -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
