Yep, your right it is not a parent. I learned that in my journey trying to
figure out this issue. Just part of the page that you can stick out there
by itself for a minute. Understanding this concept does help a great deal
when using cfwindow.
Wish I would have grasped that at the very
Can you please explain to me why you call it the parent page?
From what I can tell the cfwindow is called from the page request called, if
that is the case there is no such thing as a parent page!!
Even though it looks like a window and behaves like a window, doesnt make it
a child in the
Nando,
Thanks for the reply. This got me going down the right path. As you
mentioned I also seemed to be having an issue where the values were
persisted after the page was refreshed causing them not to show up correclty
on the main page.
The solution for me was to use :
cfajaxproxy bind=
Can you post a snippet that illustrates the problem.
The other thing to remember is that CFWindow is not a child to the browser,
it is actually just a div container within the HTML document that with style
sheets changes the look of the div to look like a window.
As I have done what you are
I also had to tackle this problem in the particular context of the data in a
cfgrid. I didn't need to refresh the whole page, but the problem seem to be
that the grid would refresh before the changes made in the cfwindow fields
were persisted. Perhaps the same is happening in your case?
The
I am using a cfwindow that opens and displays some ajax based cfselects and
a 2 date selection input fields.
This all works except when I close the window, the parent page does not
refresh the values. The page seems to refresh and I know the values have
been correctly set, but they do not show
6 matches
Mail list logo
