You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@royale.apache.org by Serkan Taş <se...@likyateknoloji.com> on 2020/03/12 05:53:34 UTC
selectionChange of MX ADG is not implemented
Hi Alex,
I migrated to AdvancedDataGrid. Need selectionChange event to change
the content of panel according to the selected line on grid.
But I am getting exception for the selectionChange handler does not exist.
Should I create a GH issue ?
Thanks,
Serkan
Re: selectionChange of MX ADG is not implemented
Posted by Serkan Taş <se...@likyateknoloji.com>.
It is really good Alex in terms of performance
Serkan
15.03.2020 21:19 tarihinde Serkan Taş yazdı:
> I just pulled and building Alex,
>
> Thanks
>
> 15.03.2020 20:23 tarihinde Alex Harui yazdı:
>>
>> I pushed some changes that optimized for fewer ADG layout passes.
>> See if it helps bring that 5-6 seconds down to 3-ish.
>>
>> -Alex
>>
>> *From: *Serkan Taş <se...@likyateknoloji.com>
>> *Date: *Saturday, March 14, 2020 at 9:41 PM
>> *To: *Alex Harui <ah...@adobe.com>, "users@royale.apache.org"
>> <us...@royale.apache.org>
>> *Subject: *Re: selectionChange of MX ADG is not implemented
>>
>> Hi Alex,
>>
>> I checked by putting traces to flex and can say that it is around 3
>> secs.
>>
>> For royale i realized that the most time consuming part is the
>> browser logging not related with royale.
>>
>> After closing the browser console it gets around 5-6 secs which is
>> acceptable.
>>
>> Thanks,
>> Serkan
>>
>> 14.03.2020 19:48 tarihinde Alex Harui yazdı:
>>
>> Can you summarize the comparison between Flex and Royale? I
>> think you are saying the Flex app takes 7 seconds and the Royale
>> takes 14 or 16?
>>
>> -Alex
>>
>> *From: *Serkan Taş <se...@likyateknoloji.com>
>> <ma...@likyateknoloji.com>
>> *Date: *Saturday, March 14, 2020 at 12:12 AM
>> *To: *"users@royale.apache.org" <ma...@royale.apache.org>
>> <us...@royale.apache.org> <ma...@royale.apache.org>, Alex
>> Harui <ah...@adobe.com> <ma...@adobe.com>
>> *Subject: *Re: selectionChange of MX ADG is not implemented
>>
>> It takes around 16 secs to finalize the view display.
>>
>> According to network view, 2.30 secs of the time consumed is the
>> "rest call" duration.
>>
>> it takes nearly 14 secs to prepare the view
>>
>> 13.03.2020 20:59 tarihinde Alex Harui yazdı:
>>
>> One way we created tests was to add a couple of buttons to
>> the app. You make a copy of the result handler and comment
>> out code in the original that sets the data provider. The
>> first button makes the server call. The other runs the code
>> that sets the data provider.
>>
>> HTH,
>>
>> -Alex
>>
>> *From: *Serkan Taş <se...@likyateknoloji.com>
>> <ma...@likyateknoloji.com>
>> *Reply-To: *"users@royale.apache.org"
>> <ma...@royale.apache.org> <us...@royale.apache.org>
>> <ma...@royale.apache.org>, "users@royale.apache.org"
>> <ma...@royale.apache.org> <us...@royale.apache.org>
>> <ma...@royale.apache.org>
>> *Date: *Thursday, March 12, 2020 at 11:40 PM
>> *To: *"users@royale.apache.org"
>> <ma...@royale.apache.org> <us...@royale.apache.org>
>> <ma...@royale.apache.org>
>> *Subject: *Re: selectionChange of MX ADG is not implemented
>>
>>
>>
>>
>>
>> It is hard to determine Alex.
>>
>> For flex, the grid is populated through a rest service
>> and it takes 3 sec to load the grid data of six lines
>> including the rest service call. But the flex app is
>> fully loaded by default.
>>
>> For Royale;
>>
>>
>>
>>
>> with one column custom renderer with 6 columns it gets
>> around 7 secs to fully load and display for the test case.
>>
>> I commented out the custom renderer and it gets around
>> 5.5 secs.
>>
>> Needs more investigation. I am going to work on try to
>> discover how to measure and improve performance if necessary.
>>
>> Thanks,
>> Serkan
>>
>> 13.03.2020 07:53 tarihinde Alex Harui yazdı:
>>
>> Try commenting out all of the custom item renderers.
>> That will tell you if the custom renderers are the
>> culprit. I don’t know what your production renderers
>> look like, but the ones in the test case looked
>> potentially heavy.
>>
>> What is the load time in your Flex app?
>>
>> -Alex
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
Re: selectionChange of MX ADG is not implemented
Posted by Serkan Taş <se...@likyateknoloji.com>.
I just pulled and building Alex,
Thanks
15.03.2020 20:23 tarihinde Alex Harui yazdı:
>
> I pushed some changes that optimized for fewer ADG layout passes. See
> if it helps bring that 5-6 seconds down to 3-ish.
>
> -Alex
>
> *From: *Serkan Taş <se...@likyateknoloji.com>
> *Date: *Saturday, March 14, 2020 at 9:41 PM
> *To: *Alex Harui <ah...@adobe.com>, "users@royale.apache.org"
> <us...@royale.apache.org>
> *Subject: *Re: selectionChange of MX ADG is not implemented
>
> Hi Alex,
>
> I checked by putting traces to flex and can say that it is around 3 secs.
>
> For royale i realized that the most time consuming part is the browser
> logging not related with royale.
>
> After closing the browser console it gets around 5-6 secs which is
> acceptable.
>
> Thanks,
> Serkan
>
> 14.03.2020 19:48 tarihinde Alex Harui yazdı:
>
> Can you summarize the comparison between Flex and Royale? I think
> you are saying the Flex app takes 7 seconds and the Royale takes
> 14 or 16?
>
> -Alex
>
> *From: *Serkan Taş <se...@likyateknoloji.com>
> <ma...@likyateknoloji.com>
> *Date: *Saturday, March 14, 2020 at 12:12 AM
> *To: *"users@royale.apache.org" <ma...@royale.apache.org>
> <us...@royale.apache.org> <ma...@royale.apache.org>, Alex
> Harui <ah...@adobe.com> <ma...@adobe.com>
> *Subject: *Re: selectionChange of MX ADG is not implemented
>
> It takes around 16 secs to finalize the view display.
>
> According to network view, 2.30 secs of the time consumed is the
> "rest call" duration.
>
> it takes nearly 14 secs to prepare the view
>
> 13.03.2020 20:59 tarihinde Alex Harui yazdı:
>
> One way we created tests was to add a couple of buttons to the
> app. You make a copy of the result handler and comment out
> code in the original that sets the data provider. The first
> button makes the server call. The other runs the code that
> sets the data provider.
>
> HTH,
>
> -Alex
>
> *From: *Serkan Taş <se...@likyateknoloji.com>
> <ma...@likyateknoloji.com>
> *Reply-To: *"users@royale.apache.org"
> <ma...@royale.apache.org> <us...@royale.apache.org>
> <ma...@royale.apache.org>, "users@royale.apache.org"
> <ma...@royale.apache.org> <us...@royale.apache.org>
> <ma...@royale.apache.org>
> *Date: *Thursday, March 12, 2020 at 11:40 PM
> *To: *"users@royale.apache.org"
> <ma...@royale.apache.org> <us...@royale.apache.org>
> <ma...@royale.apache.org>
> *Subject: *Re: selectionChange of MX ADG is not implemented
>
>
>
>
>
> It is hard to determine Alex.
>
> For flex, the grid is populated through a rest service and
> it takes 3 sec to load the grid data of six lines
> including the rest service call. But the flex app is fully
> loaded by default.
>
> For Royale;
>
>
>
>
> with one column custom renderer with 6 columns it gets
> around 7 secs to fully load and display for the test case.
>
> I commented out the custom renderer and it gets around 5.5
> secs.
>
> Needs more investigation. I am going to work on try to
> discover how to measure and improve performance if necessary.
>
> Thanks,
> Serkan
>
> 13.03.2020 07:53 tarihinde Alex Harui yazdı:
>
> Try commenting out all of the custom item renderers.
> That will tell you if the custom renderers are the
> culprit. I don’t know what your production renderers
> look like, but the ones in the test case looked
> potentially heavy.
>
> What is the load time in your Flex app?
>
> -Alex
>
>
>
>
>
>
>
>
>
>
Re: selectionChange of MX ADG is not implemented
Posted by Alex Harui <ah...@adobe.com>.
I pushed some changes that optimized for fewer ADG layout passes. See if it helps bring that 5-6 seconds down to 3-ish.
-Alex
From: Serkan Taş <se...@likyateknoloji.com>
Date: Saturday, March 14, 2020 at 9:41 PM
To: Alex Harui <ah...@adobe.com>, "users@royale.apache.org" <us...@royale.apache.org>
Subject: Re: selectionChange of MX ADG is not implemented
Hi Alex,
I checked by putting traces to flex and can say that it is around 3 secs.
For royale i realized that the most time consuming part is the browser logging not related with royale.
After closing the browser console it gets around 5-6 secs which is acceptable.
Thanks,
Serkan
14.03.2020 19:48 tarihinde Alex Harui yazdı:
Can you summarize the comparison between Flex and Royale? I think you are saying the Flex app takes 7 seconds and the Royale takes 14 or 16?
-Alex
From: Serkan Taş <se...@likyateknoloji.com>
Date: Saturday, March 14, 2020 at 12:12 AM
To: "users@royale.apache.org"<ma...@royale.apache.org> <us...@royale.apache.org>, Alex Harui <ah...@adobe.com>
Subject: Re: selectionChange of MX ADG is not implemented
It takes around 16 secs to finalize the view display.
According to network view, 2.30 secs of the time consumed is the "rest call" duration.
it takes nearly 14 secs to prepare the view
[cid:image001.png@01D5FAB3.C223BE30]
13.03.2020 20:59 tarihinde Alex Harui yazdı:
One way we created tests was to add a couple of buttons to the app. You make a copy of the result handler and comment out code in the original that sets the data provider. The first button makes the server call. The other runs the code that sets the data provider.
HTH,
-Alex
From: Serkan Taş <se...@likyateknoloji.com>
Reply-To: "users@royale.apache.org"<ma...@royale.apache.org> <us...@royale.apache.org>, "users@royale.apache.org"<ma...@royale.apache.org> <us...@royale.apache.org>
Date: Thursday, March 12, 2020 at 11:40 PM
To: "users@royale.apache.org"<ma...@royale.apache.org> <us...@royale.apache.org>
Subject: Re: selectionChange of MX ADG is not implemented
It is hard to determine Alex.
For flex, the grid is populated through a rest service and it takes 3 sec to load the grid data of six lines including the rest service call. But the flex app is fully loaded by default.
[cid:image002.png@01D5FAB3.C223BE30]
For Royale;
with one column custom renderer with 6 columns it gets around 7 secs to fully load and display for the test case.
I commented out the custom renderer and it gets around 5.5 secs.
Needs more investigation. I am going to work on try to discover how to measure and improve performance if necessary.
Thanks,
Serkan
13.03.2020 07:53 tarihinde Alex Harui yazdı:
Try commenting out all of the custom item renderers. That will tell you if the custom renderers are the culprit. I don’t know what your production renderers look like, but the ones in the test case looked potentially heavy.
What is the load time in your Flex app?
-Alex
Re: selectionChange of MX ADG is not implemented
Posted by Serkan Taş <se...@likyateknoloji.com>.
Hi Alex,
I checked by putting traces to flex and can say that it is around 3 secs.
For royale i realized that the most time consuming part is the browser
logging not related with royale.
After closing the browser console it gets around 5-6 secs which is
acceptable.
Thanks,
Serkan
14.03.2020 19:48 tarihinde Alex Harui yazdı:
>
> Can you summarize the comparison between Flex and Royale? I think you
> are saying the Flex app takes 7 seconds and the Royale takes 14 or 16?
>
> -Alex
>
> *From: *Serkan Taş <se...@likyateknoloji.com>
> *Date: *Saturday, March 14, 2020 at 12:12 AM
> *To: *"users@royale.apache.org" <us...@royale.apache.org>, Alex Harui
> <ah...@adobe.com>
> *Subject: *Re: selectionChange of MX ADG is not implemented
>
> It takes around 16 secs to finalize the view display.
>
> According to network view, 2.30 secs of the time consumed is the "rest
> call" duration.
>
> it takes nearly 14 secs to prepare the view
>
> 13.03.2020 20:59 tarihinde Alex Harui yazdı:
>
> One way we created tests was to add a couple of buttons to the
> app. You make a copy of the result handler and comment out code in
> the original that sets the data provider. The first button makes
> the server call. The other runs the code that sets the data provider.
>
> HTH,
>
> -Alex
>
> *From: *Serkan Taş <se...@likyateknoloji.com>
> <ma...@likyateknoloji.com>
> *Reply-To: *"users@royale.apache.org"
> <ma...@royale.apache.org> <us...@royale.apache.org>
> <ma...@royale.apache.org>, "users@royale.apache.org"
> <ma...@royale.apache.org> <us...@royale.apache.org>
> <ma...@royale.apache.org>
> *Date: *Thursday, March 12, 2020 at 11:40 PM
> *To: *"users@royale.apache.org" <ma...@royale.apache.org>
> <us...@royale.apache.org> <ma...@royale.apache.org>
> *Subject: *Re: selectionChange of MX ADG is not implemented
>
>
>
>
> It is hard to determine Alex.
>
> For flex, the grid is populated through a rest service and it
> takes 3 sec to load the grid data of six lines including the
> rest service call. But the flex app is fully loaded by default.
>
> For Royale;
>
>
>
> with one column custom renderer with 6 columns it gets around
> 7 secs to fully load and display for the test case.
>
> I commented out the custom renderer and it gets around 5.5 secs.
>
> Needs more investigation. I am going to work on try to
> discover how to measure and improve performance if necessary.
>
> Thanks,
> Serkan
>
> 13.03.2020 07:53 tarihinde Alex Harui yazdı:
>
> Try commenting out all of the custom item renderers. That
> will tell you if the custom renderers are the culprit. I
> don’t know what your production renderers look like, but
> the ones in the test case looked potentially heavy.
>
> What is the load time in your Flex app?
>
> -Alex
>
>
>
>
>
>
Re: selectionChange of MX ADG is not implemented
Posted by Alex Harui <ah...@adobe.com>.
Can you summarize the comparison between Flex and Royale? I think you are saying the Flex app takes 7 seconds and the Royale takes 14 or 16?
-Alex
From: Serkan Taş <se...@likyateknoloji.com>
Date: Saturday, March 14, 2020 at 12:12 AM
To: "users@royale.apache.org" <us...@royale.apache.org>, Alex Harui <ah...@adobe.com>
Subject: Re: selectionChange of MX ADG is not implemented
It takes around 16 secs to finalize the view display.
According to network view, 2.30 secs of the time consumed is the "rest call" duration.
it takes nearly 14 secs to prepare the view
[cid:image001.png@01D5F9E5.AD83CA20]
13.03.2020 20:59 tarihinde Alex Harui yazdı:
One way we created tests was to add a couple of buttons to the app. You make a copy of the result handler and comment out code in the original that sets the data provider. The first button makes the server call. The other runs the code that sets the data provider.
HTH,
-Alex
From: Serkan Taş <se...@likyateknoloji.com>
Reply-To: "users@royale.apache.org"<ma...@royale.apache.org> <us...@royale.apache.org>, "users@royale.apache.org"<ma...@royale.apache.org> <us...@royale.apache.org>
Date: Thursday, March 12, 2020 at 11:40 PM
To: "users@royale.apache.org"<ma...@royale.apache.org> <us...@royale.apache.org>
Subject: Re: selectionChange of MX ADG is not implemented
It is hard to determine Alex.
For flex, the grid is populated through a rest service and it takes 3 sec to load the grid data of six lines including the rest service call. But the flex app is fully loaded by default.
[cid:image002.png@01D5F9E5.AD83CA20]
For Royale;
with one column custom renderer with 6 columns it gets around 7 secs to fully load and display for the test case.
I commented out the custom renderer and it gets around 5.5 secs.
Needs more investigation. I am going to work on try to discover how to measure and improve performance if necessary.
Thanks,
Serkan
13.03.2020 07:53 tarihinde Alex Harui yazdı:
Try commenting out all of the custom item renderers. That will tell you if the custom renderers are the culprit. I don’t know what your production renderers look like, but the ones in the test case looked potentially heavy.
What is the load time in your Flex app?
-Alex
Re: selectionChange of MX ADG is not implemented
Posted by Serkan Taş <se...@likyateknoloji.com>.
It takes around 16 secs to finalize the view display.
According to network view, 2.30 secs of the time consumed is the "rest
call" duration.
it takes nearly 14 secs to prepare the view
13.03.2020 20:59 tarihinde Alex Harui yazdı:
>
> One way we created tests was to add a couple of buttons to the app.
> You make a copy of the result handler and comment out code in the
> original that sets the data provider. The first button makes the
> server call. The other runs the code that sets the data provider.
>
> HTH,
>
> -Alex
>
> *From: *Serkan Taş <se...@likyateknoloji.com>
> *Reply-To: *"users@royale.apache.org" <us...@royale.apache.org>,
> "users@royale.apache.org" <us...@royale.apache.org>
> *Date: *Thursday, March 12, 2020 at 11:40 PM
> *To: *"users@royale.apache.org" <us...@royale.apache.org>
> *Subject: *Re: selectionChange of MX ADG is not implemented
>
>
>
> It is hard to determine Alex.
>
> For flex, the grid is populated through a rest service and it
> takes 3 sec to load the grid data of six lines including the rest
> service call. But the flex app is fully loaded by default.
>
> For Royale;
>
>
> with one column custom renderer with 6 columns it gets around 7
> secs to fully load and display for the test case.
>
> I commented out the custom renderer and it gets around 5.5 secs.
>
> Needs more investigation. I am going to work on try to discover
> how to measure and improve performance if necessary.
>
> Thanks,
> Serkan
>
> 13.03.2020 07:53 tarihinde Alex Harui yazdı:
>
> Try commenting out all of the custom item renderers. That
> will tell you if the custom renderers are the culprit. I
> don’t know what your production renderers look like, but the
> ones in the test case looked potentially heavy.
>
> What is the load time in your Flex app?
>
> -Alex
>
>
>
Re: selectionChange of MX ADG is not implemented
Posted by Alex Harui <ah...@adobe.com>.
One way we created tests was to add a couple of buttons to the app. You make a copy of the result handler and comment out code in the original that sets the data provider. The first button makes the server call. The other runs the code that sets the data provider.
HTH,
-Alex
From: Serkan Taş <se...@likyateknoloji.com>
Reply-To: "users@royale.apache.org" <us...@royale.apache.org>, "users@royale.apache.org" <us...@royale.apache.org>
Date: Thursday, March 12, 2020 at 11:40 PM
To: "users@royale.apache.org" <us...@royale.apache.org>
Subject: Re: selectionChange of MX ADG is not implemented
It is hard to determine Alex.
For flex, the grid is populated through a rest service and it takes 3 sec to load the grid data of six lines including the rest service call. But the flex app is fully loaded by default.
[cid:image001.png@01D5F926.6D669310]
For Royale;
with one column custom renderer with 6 columns it gets around 7 secs to fully load and display for the test case.
I commented out the custom renderer and it gets around 5.5 secs.
Needs more investigation. I am going to work on try to discover how to measure and improve performance if necessary.
Thanks,
Serkan
13.03.2020 07:53 tarihinde Alex Harui yazdı:
Try commenting out all of the custom item renderers. That will tell you if the custom renderers are the culprit. I don’t know what your production renderers look like, but the ones in the test case looked potentially heavy.
What is the load time in your Flex app?
-Alex
Re: selectionChange of MX ADG is not implemented
Posted by Serkan Taş <se...@likyateknoloji.com>.
> It is hard to determine Alex.
>
> For flex, the grid is populated through a rest service and it takes 3
> sec to load the grid data of six lines including the rest service
> call. But the flex app is fully loaded by default.
>
>
>
For Royale;
> with one column custom renderer with 6 columns it gets around 7 secs
> to fully load and display for the test case.
>
> I commented out the custom renderer and it gets around 5.5 secs.
>
> Needs more investigation. I am going to work on try to discover how to
> measure and improve performance if necessary.
>
> Thanks,
> Serkan
>
> 13.03.2020 07:53 tarihinde Alex Harui yazdı:
>>
>> Try commenting out all of the custom item renderers. That will tell
>> you if the custom renderers are the culprit. I don’t know what your
>> production renderers look like, but the ones in the test case looked
>> potentially heavy.
>>
>> What is the load time in your Flex app?
>>
>> -Alex
>>
>>
>
Re: selectionChange of MX ADG is not implemented
Posted by Serkan Taş <se...@likyateknoloji.com>.
It is hard to determine Alex.
For flex, the grid is populated through a rest service and it takes 3
sec to load the grid data of six lines including the rest service call.
But the flex app is fully loaded by default.
with one column custom renderer with 6 columns it gets around 7 secs to
fully load and display for the test case.
I commented out the custom renderer and it gets around 5.5 secs.
Needs more investigation. I am going to work on try to discover how to
measure and improve performance if necessary.
Thanks,
Serkan
13.03.2020 07:53 tarihinde Alex Harui yazdı:
>
> Try commenting out all of the custom item renderers. That will tell
> you if the custom renderers are the culprit. I don’t know what your
> production renderers look like, but the ones in the test case looked
> potentially heavy.
>
> What is the load time in your Flex app?
>
> -Alex
>
>
Re: selectionChange of MX ADG is not implemented
Posted by Alex Harui <ah...@adobe.com>.
Try commenting out all of the custom item renderers. That will tell you if the custom renderers are the culprit. I don’t know what your production renderers look like, but the ones in the test case looked potentially heavy.
What is the load time in your Flex app?
-Alex
From: Serkan Taş <se...@likyateknoloji.com>
Date: Thursday, March 12, 2020 at 3:00 PM
To: "users@royale.apache.org" <us...@royale.apache.org>, Alex Harui <ah...@adobe.com>
Subject: Re: selectionChange of MX ADG is not implemented
Confirm !
It is working for "change" Alex thanks.
I have another question. MX ADG load time is around 6-7 secs. Even it has only two lines on grid for the test case.
Lines of logs at console as below :
[cid:image001.png@01D5F8B8.A6429530]
For the real application takes more around 12 secs and at last I get exception below :
[cid:image002.png@01D5F8B8.A6429530]
I am trying trying to discover the reason and some help may be needed.
Thanks,
Serkan
12.03.2020 09:35 tarihinde Alex Harui yazdı:
We discussed this on March 1. I wrote: “Pretty sure Spark DG “selectionChange” is just “change” for MX ADG”.
Is that not the case? I have to stop work for tonight. I will check for your reply tomorrow.
-Alex
From: Serkan Taş <se...@likyateknoloji.com>
Reply-To: "users@royale.apache.org"<ma...@royale.apache.org> <us...@royale.apache.org>
Date: Wednesday, March 11, 2020 at 10:54 PM
To: "users@royale.apache.org"<ma...@royale.apache.org> <us...@royale.apache.org>
Subject: selectionChange of MX ADG is not implemented
Hi Alex,
I migrated to AdvancedDataGrid. Need selectionChange event to change the content of panel according to the selected line on grid.
But I am getting exception for the selectionChange handler does not exist.
[cid:image003.png@01D5F8B8.A6429530]
Should I create a GH issue ?
Thanks,
Serkan
Re: selectionChange of MX ADG is not implemented
Posted by Serkan Taş <se...@likyateknoloji.com>.
Confirm !
It is working for "change" Alex thanks.
I have another question. MX ADG load time is around 6-7 secs. Even it
has only two lines on grid for the test case.
Lines of logs at console as below :
For the real application takes more around 12 secs and at last I get
exception below :
I am trying trying to discover the reason and some help may be needed.
Thanks,
Serkan
12.03.2020 09:35 tarihinde Alex Harui yazdı:
>
> We discussed this on March 1. I wrote: “Pretty sure Spark DG
> “selectionChange” is just “change” for MX ADG”.
>
> Is that not the case? I have to stop work for tonight. I will check
> for your reply tomorrow.
>
> -Alex
>
> *From: *Serkan Taş <se...@likyateknoloji.com>
> *Reply-To: *"users@royale.apache.org" <us...@royale.apache.org>
> *Date: *Wednesday, March 11, 2020 at 10:54 PM
> *To: *"users@royale.apache.org" <us...@royale.apache.org>
> *Subject: *selectionChange of MX ADG is not implemented
>
> Hi Alex,
>
> I migrated to AdvancedDataGrid. Need selectionChange event to change
> the content of panel according to the selected line on grid.
>
> But I am getting exception for the selectionChange handler does not exist.
>
>
>
> Should I create a GH issue ?
>
> Thanks,
> Serkan
>
>
>
Re: selectionChange of MX ADG is not implemented
Posted by Alex Harui <ah...@adobe.com>.
We discussed this on March 1. I wrote: “Pretty sure Spark DG “selectionChange” is just “change” for MX ADG”.
Is that not the case? I have to stop work for tonight. I will check for your reply tomorrow.
-Alex
From: Serkan Taş <se...@likyateknoloji.com>
Reply-To: "users@royale.apache.org" <us...@royale.apache.org>
Date: Wednesday, March 11, 2020 at 10:54 PM
To: "users@royale.apache.org" <us...@royale.apache.org>
Subject: selectionChange of MX ADG is not implemented
Hi Alex,
I migrated to AdvancedDataGrid. Need selectionChange event to change the content of panel according to the selected line on grid.
But I am getting exception for the selectionChange handler does not exist.
[cid:image001.png@01D5F7FD.C9B29C10]
Should I create a GH issue ?
Thanks,
Serkan