06-12-2019, 10:37 AM
Hi Francesco,
i got the same problem with
C++Builder 10.3 Update 1 and
IntraWeb 15.0.22 Ultimate edition.
The problem seems to be related to the TIWFrameRegion object which is created for each frame automatically.
My workaround was to create a separate content region with different names below IWFrameRegion and initialize as follows:
// Create first frame
FFrameInput->IWFrameRegion->Parent = NULL;
FFrameInput->IWFrameRegion->Visible = false;
FFrameInput->IWFrameRegionInput->Parent = this;
FFrameInput->IWFrameRegionInput->Visible = false;
// Create first frame
FFrameFilter->IWFrameRegion->Parent = NULL;
FFrameFilter->IWFrameRegion->Visible = false;
FFrameFilter->IWFrameRegionFilter->Parent = this;
FFrameFilter->IWFrameRegionFilter->Visible = false;
You don't need to use two TIWModalWindow objects if you assign the event handler dynamically.
Jürgen
i got the same problem with
C++Builder 10.3 Update 1 and
IntraWeb 15.0.22 Ultimate edition.
The problem seems to be related to the TIWFrameRegion object which is created for each frame automatically.
My workaround was to create a separate content region with different names below IWFrameRegion and initialize as follows:
// Create first frame
FFrameInput->IWFrameRegion->Parent = NULL;
FFrameInput->IWFrameRegion->Visible = false;
FFrameInput->IWFrameRegionInput->Parent = this;
FFrameInput->IWFrameRegionInput->Visible = false;
// Create first frame
FFrameFilter->IWFrameRegion->Parent = NULL;
FFrameFilter->IWFrameRegion->Visible = false;
FFrameFilter->IWFrameRegionFilter->Parent = this;
FFrameFilter->IWFrameRegionFilter->Visible = false;
You don't need to use two TIWModalWindow objects if you assign the event handler dynamically.
Jürgen