Hi Peter,
We have some flex developers here who mentioned that cf7 flash stuff is based in flex 1.5.
I have isolated the issue into some sample code that you can run and make sense of my convoluted explanation.
Here is some sample code that demonstrates this, when you first load it try clicking on the column(not the checkboxes) to activate the onChange on the cfgrid. It will not correctly update the cfinput:checkbox value. However if you manually change the checkbox's in the cfgrid and then try the same it works correctly :
<cfset aValues = arrayNew(1)>
<cfset aValues[1] = true>
<cfset aValues[2] = false>
<cfset aValues[3] = true>
<cfset aValues[4] = false>
<cfset aValues[5] = true>
<cfset qTest = queryNew("")>
<cfset queryaddColumn(qTest,"test_column","bit",aValues)>
<cfform format="Flash">
<cfgrid name="gTest" height="250" width="550" format="FLASH" query="qTest" selectmode="EDIT" = Boolean(gTest.dataProvider[gTest.selectedIndex]['test_column'])">
<cfgridcolumn name="test_column" header="test_column" width="40" select="Yes" display="Yes" type="BOOLEAN" headerbold="No">
</cfgrid>
<cfinput type="Checkbox" name="test_column" label="Test:" 'test_column', test_column.selected );" visible="Yes" enabled="Yes">
</cfform>
-----Original Message-----
From: Peter Tilbrook [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 4 May 2005 6:12 PM
To: CFAussie Mailing List
Subject: [cfaussie] RE: Cf7 cfgrid.
Theo, I'd like to see your code.
I'm starting to get pretty good at this "binding" stuff. Especially with CFGRID.
After an issue with linking to the KEY value of a Verity (query) result the problem was I used 'Key' and not 'KEY' a subtle difference which not even Mike Nimer was aware.
Remember this however - the Flash forms in CFMX7 (CFGRID for example) are based on controls found in Macromedia Flex (either 1.0 or 1.5, possibly only
1.0) but the CFMX7 Flash forms are NOT Flex forms.
Yes they look similar (ColdFusion to Flex), however they operate in a dis-similar fashion. Unlike Flex, CFMX7 forms must be "submitted" like a standard HTTP or HTTPS form in order to function.
Flex can utilise different methods (and not require a screen refresh) to do this.
CFMX7 Flash forms have a way to go yet but even if using the standard HTML
(CFFORM) version the better validation and other improvements are a godsend.
The issue I encountered with the following line of code:
<cfgrid name="SearchResults" rowheaders="no" gridlines="no" colheaderbold="yes" query="SearchSite" + SearchResults.dataProvider[SearchResults.selectedIndex]['Key']);">
Appeared to be the fact that the last 'Key' should have been UPPERCASE, eg: ['KEY'] - even the MM gurus were stumped. I believe this is a bug but.... But I persisted and so should you.
Flash forms are not Flex but they are a good start - and there is still Xforms too! Remember that CFMX 7 is OK for Flash forms but Flex was designed for true RIA applications.
Peter Tilbrook
ColdGen Internet Solutions
Manager, ACT and Region ColdFusion Users Group
PO Box 2247
Queanbeyan, NSW, 2620
AUSTRALIA
WWW 1: http://www.coldgen.com/
WWW 2: http://www.actcfug.com/
Telephone: +61-2-6284-2727
Mobile: 0432 897 437
E-mail: [EMAIL PROTECTED]
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
| ______________________________________________________________________ This email, including attachments, is intended only for the addressee and may be confidential, privileged and subject to copyright. If you have received this email in error, please advise the sender and delete it. If you are not the intended recipient of this email, you must not use, copy or disclose its content to anyone. You must not copy or communicate to others content that is confidential or subject to copyright, unless you have the consent of the content owner. |
