Skip to main content
Inspiring
March 24, 2008
Question

CFWINDOW problem

  • March 24, 2008
  • 12 replies
  • 3080 views
Can't figure out why in two cfwindows created from main page, calendar in cfinput type="datefield" behaves differently depending on ORDER in which they created. Calendar icon became inactive in the second window if the first one was called and then closed. (The input field is still active for manual data entry). But if main page refreshed it's active again. In the first window the calendar active at any time without refreshing main page and when called in any order. These 2 windows are identical. Bahavior is the same with any settings of cfwindow attriburtes like refreshOnShow (true or false) and others. And if to switch the order of windows creation in main page, the calendar in the other pop-up window became frozen and first one previously inactive works fine. Is it a bug in CF8?
This is code in main page:
<cfajaximport tags="cfwindow, cfform, cfinput-datefield" >
<cfwindow title="WindowName1"
name="MyName1"
height="380"
modal="false"
refreshOnShow="true"
initShow="false"
source="../MySource1.cfm"/ >

<cfwindow title="WindowName2"
name="MyName2"
height="380"
modal="false"
refreshOnShow="true"
initShow="false"
source="../MySource2.cfm"/ >

Calles for pop-up windows:
<a href="#" onclick="javascript:ColdFusion.Window.show(MyName1);">Title 1</a>
<a href="#" onclick="javascript:ColdFusion.Window.show(MyName2);">Title 2</a>

in called windows:
<cfform>
<cfinput type="datefield" name="FieldName1">
.......
</cfform>

<cfform>
<cfinput type="datefield" name="FieldName2">
.......
</cfform>




This topic has been closed for replies.

12 replies

March 24, 2008
I find cfwindow buggy as well. And considering the touting that cf8 has cool features for Use Experience, I believe Adobe can do better if they put in more and Better resources into it. As a community we would all benefit from it... Unfortunately it seems that Adobe has adopted a "raising cows" business model for creating zillions of products. Another strategy would be partially "raising cows" but still got flagship products including Cold Fusion 8...
this strategy would be a win-win for Adobe and us.
Inspiring
March 24, 2008
I've tried using cfWindow and I found out that it's too buggy. It would work on FF but it wouldn't on IE and vice versa. And then when you add flash forms into it it just goes crazy. don't worry, there is perfect solution for it, CF_Window custom tag, it's free and it works great.
http://cfwindow.riaforge.org/
CF_OracleAuthor
Inspiring
March 24, 2008
TiGGi, thank you for quick reply. Yes it works fine in Fireforks browser but our client has IE. We'll see what Adobe will say on this issue.