FluentSelect go into infinite SelectedOptionChanged calls #3807
Replies: 5 comments 1 reply
-
We'd need something we can actually run if you want us to look at it. Otherwise it will just continue to be a guessing game. |
Beta Was this translation helpful? Give feedback.
-
@vnbaaij |
Beta Was this translation helpful? Give feedback.
-
@vnbaaij |
Beta Was this translation helpful? Give feedback.
-
@elendil-software I took a look on your project and I think this has something todo with the structure itself. You are passing the same item from component to component. And I think when the parameter will be set in component 3 it tells component to to set the new parameter. When the paramater in component 2 changes it will trigger component 3 again. Usually you would either cascade all parameters down using |
Beta Was this translation helpful? Give feedback.
-
Hi, I reworked my test project :
Even with these modifications it keep looping on I also tried a CascadingParameter as sugested by @MarvinKlein1508 but I get the same result. As an additionnal step I also tried to put the I also noticed a huge memory consumption (~10 MB/sec) as soon as I try to change the selected item |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have a component containing a form and it use a child componenant containing a
FluentSelect
. The option to be selected is passed by parameter to the component.My problem is that it keeps calling
SelectedOptionChanged
as soon as the parameter is set by the parent. And the parameter passed toOnSelectedOptionChanged
is alwaysnull
The parent component :
the child component (
IPX800Select
)What am I doing wrong ?
Beta Was this translation helpful? Give feedback.
All reactions