[flexcoders] Accessing Multi Dimensional Array Collection Data in a DataGrid
Hi there, Probably a rather straightforward solution that I am just overlooking. I have an array collection that is acting as the data provider for a datagrid. I have mapped out all the columns between the array collection and the data grid with the DataGridColumn element. However, my array collection is multi dimensional, and I can't figure out how to map "deeper" content to the data field. The each collection row contains a nested array called "practice" that has values. How do I map my datagrid column to the "name" property of the nested array "practice"? Thanks, Mike
[flexcoders] Opening the Browser From AIR
Hi there, Silly question that I can't seem to find any tips on. Can I launch the native OS browser via a Flex app running on AIR? Thanks! Mike
[flexcoders] Re: Opening the Browser From AIR
Sorry to respond to my own thread here, but maybe the lack of response is due to my lack of a good example. In my MXML I have a linkButton that I would like to pop the system browser pointed to a particular URL. My code looks like this: http://www.adobe.com/2006/mxml"; layout="vertical" viewSourceURL="srcview/index.html"> Well, this ends up popping my default text editor with the raw HTML. This has got to be doable. What am I missing here? Thanks, Mike
[flexcoders] Spark DropDownList Items Tooltip
Hi there, I'm trying to figure out how to add tool tips for a hovered list item in a spark dropdownlist. This guy posted how to accomplish this with combobox: http://raghuonflex.wordpress.com/2007/09/19/tooltips-for-combobox-items-or-list-items/ Any "tips" on doing the same thing with the spark dropdownlist? Thanks, Mike
[flexcoders] WebService Payload Truncated (#2006 Out of Bounds Error) on Send in Gumbo
Hi, I have a problem sending a large base64Binary parameter as part of a SOAP body using Gumbo build 9127. The payload generated by Flex to be sent looks like this (truncated for brevity): http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://schemas.xmlsoap.org/soap/encoding/";> SCANNER_374_090511_1201_full.cal AABAQAAAu0MAAAzCMxEPwtSDDsKjRonCAAAWQ3JQtDwK1yM8eFMfvArX...IXD3uCWusQSh70AkBpBAPAbRpZjHEbNzKxAXE+tQA== Before the entire payload is sent, my responder fault handler is receiving an "Error #2006: The supplied index is out of bounds.". The responder result handler is shortly after triggered, with the result form the web service. Looking at the raw data sent over the wire using Wireshark, I was able to see that Flex is truncating on send the contents of the parameter (pFileContent), but then completing the send of the remainder of the payload. Here is an example of what the received data looked like (note the truncation of the pFileContent element) http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://schemas.xmlsoap.org/soap/encoding/";> SCANNER_374_090511_1201_full.cal AABAQAAAu0MAAAzCMxEPwtSDDsKjRonCAAAWQ3JQtDwK1yM8eFMfvArX...IXD Any ideas what could be causing this. Any tips for debugging further? Thanks, Mike
[flexcoders] Re: WebService Payload Truncated (#2006 Out of Bounds Error) on Send in Gumbo
I've been looking at this problem for just about a day straight now, and just can't see why I'm getting an out of bounds error on send. I've tried updated to the latest Gumbo nightly (9377), which no luck. My code to launch the WebService call looks like this: _calibrationData = new ByteArray(); var stream:FileStream = new FileStream(); stream.open(file, FileMode.READ); stream.readBytes(_calibrationData, 0, stream.bytesAvailable); var token:AsyncToken = this._service.mLoadCalibration(file.name, _calibrationData); token.addResponder(this._mLoadCalibrationResponder); Which seems to be a-okay. Or, am I missing something obvious? I'm pretty sure I've hit up against a SDK bug. I've opened a bug report with Adobe, to track this issue at http://bugs.adobe.com/jira/browse/SDK-22751 Anyone else transferring "large" (1MB) base64 encoded data using the Flex webservice client? Any feedback highly welcome! Thanks, Mike
[flexcoders] Re: WebService Payload Truncated (#2006 Out of Bounds Error) on Send in Gumbo
Interesting point. I tried truncating my byte array down to 60KB, I still got the "out of bounds" fault. However, if i drop the byte array down to 10KB, no "out of bounds" error. Somewhere between the two (60KB and 10KB) is the breaking point. I've read through the article you referenced (thanks for the link!), but still don't see what quota parameter Flex would be blowing. Are we talking MaxReceivedMessageSize? The other interesting thing is that I'm seeing much greater volume than 60KB being transmitted to the SOAP server when inspecting incoming data server side using Wireshark. If this is a quota violation being triggered, how would it enforce on the packet data? Would some of it be dropped? Maybe everything following the violation? Thanks, Mike --- In flexcoders@yahoogroups.com, "valdhor" wrote: > > I wonder if you have hit a windows limitation. This article may give you some > ideas... > > http://blogs.msdn.com/drnick/archive/2006/03/10/547568.aspx > > > --- In flexcoders@yahoogroups.com, "michaelisraelcaplan" wrote: > > > > I've been looking at this problem for just about a day straight now, and > > just can't see why I'm getting an out of bounds error on send. I've tried > > updated to the latest Gumbo nightly (9377), which no luck. > > > > My code to launch the WebService call looks like this: > > > > > > _calibrationData = new ByteArray(); > > var stream:FileStream = new FileStream(); > > stream.open(file, FileMode.READ); > > stream.readBytes(_calibrationData, 0, stream.bytesAvailable); > > > > var token:AsyncToken = this._service.mLoadCalibration(file.name, > > _calibrationData); > > token.addResponder(this._mLoadCalibrationResponder); > > > > > > Which seems to be a-okay. Or, am I missing something obvious? > > > > > > I'm pretty sure I've hit up against a SDK bug. I've opened a bug report > > with Adobe, to track this issue at > > http://bugs.adobe.com/jira/browse/SDK-22751 > > > > > > Anyone else transferring "large" (1MB) base64 encoded data using the Flex > > webservice client? > > > > > > Any feedback highly welcome! > > > > Thanks, > > > > Mike > > >
[flexcoders] Re: WebService Payload Truncated (#2006 Out of Bounds Error) on Send in Gumbo
Ah, MaxReceivedMessageSize is not a Windows limit,per se, but a Windows WCF limit that is programatically controlled by the SOAP server. That shouldn't be a factor with the "out of bounds" fault? --- In flexcoders@yahoogroups.com, "michaelisraelcaplan" wrote: > > Interesting point. I tried truncating my byte array down to 60KB, I still > got the "out of bounds" fault. However, if i drop the byte array down to > 10KB, no "out of bounds" error. > > Somewhere between the two (60KB and 10KB) is the breaking point. I've read > through the article you referenced (thanks for the link!), but still don't > see what quota parameter Flex would be blowing. Are we talking > MaxReceivedMessageSize? > > > The other interesting thing is that I'm seeing much greater volume than 60KB > being transmitted to the SOAP server when inspecting incoming data server > side using Wireshark. If this is a quota violation being triggered, how > would it enforce on the packet data? Would some of it be dropped? Maybe > everything following the violation? > > Thanks, > > Mike > > > --- In flexcoders@yahoogroups.com, "valdhor" wrote: > > > > I wonder if you have hit a windows limitation. This article may give you > > some ideas... > > > > http://blogs.msdn.com/drnick/archive/2006/03/10/547568.aspx > > > > > > --- In flexcoders@yahoogroups.com, "michaelisraelcaplan" wrote: > > > > > > I've been looking at this problem for just about a day straight now, and > > > just can't see why I'm getting an out of bounds error on send. I've > > > tried updated to the latest Gumbo nightly (9377), which no luck. > > > > > > My code to launch the WebService call looks like this: > > > > > > > > > _calibrationData = new ByteArray(); > > > var stream:FileStream = new FileStream(); > > > stream.open(file, FileMode.READ); > > > stream.readBytes(_calibrationData, 0, stream.bytesAvailable); > > > > > > var token:AsyncToken = this._service.mLoadCalibration(file.name, > > > _calibrationData); > > > token.addResponder(this._mLoadCalibrationResponder); > > > > > > > > > Which seems to be a-okay. Or, am I missing something obvious? > > > > > > > > > I'm pretty sure I've hit up against a SDK bug. I've opened a bug report > > > with Adobe, to track this issue at > > > http://bugs.adobe.com/jira/browse/SDK-22751 > > > > > > > > > Anyone else transferring "large" (1MB) base64 encoded data using the Flex > > > webservice client? > > > > > > > > > Any feedback highly welcome! > > > > > > Thanks, > > > > > > Mike > > > > > >
[flexcoders] AIR ApplicationUpdaterUI Not Initializing
Hi,
I'm using the Flex SDK 4.0.0.9916, and cannot get the ApplicationUpdaterUI to
initialize.
Following creation complete, I initialize the ApplicationUpdaterUI object, and
call the ApplicationUpdaterUI.initialize() -- code snippet below.
The object appears to initialized properly according to the data popped out in
the application log:
(air.update::ApplicationUpdaterUI)#0
configurationFile = (flash.filesystem::File)#1
currentVersion = "0.2"
delay = 1
isCheckForUpdateVisible = true
isDownloadProgressVisible = true
isDownloadUpdateVisible = true
isFileUpdateVisible = true
isFirstRun = false
isInstallUpdateVisible = true
isNewerVersionFunction = (function)
isUnexpectedErrorVisible = true
isUpdateInProgress = true
localeChain = (Array)#40
previousApplicationStorageDirectory = (null)
previousVersion = ""
updateDescriptor = (null)
updateURL = "http://www.ddxint.com/service/default/desktop_update/updates.xml";
wasPendingUpdate = false
However, none of my events are being triggered. My Apache access log doesn't
show any hits on the defined URL. Also, calls to checkNow() do absolutely
nothing. The only things that I am seeing is that the user application local
store folder is being populated with an "#ApplicationUpdater" folder with a
state.xml file:
http://ns.adobe.com/air/framework/update/state/1.0";>
Thu Sep 3 16:27:37 GMT-0300 2009
This seems to show that the updater is doing something... but what?
Any ideas?
Thanks,
Mike
protected function _initializeUpdateFramework():void
{
if (!Capabilities.isDebugger) {
this.updater = new ApplicationUpdaterUI();
this.updater.configurationFile = new File("app:/assets/update.xml");
this.updater.addEventListener(DownloadErrorEvent.DOWNLOAD_ERROR,
_download);
this.updater.addEventListener(ErrorEvent.ERROR, _error);
this.updater.addEventListener(ProgressEvent.PROGRESS, _progress);
this.updater.addEventListener(StatusFileUpdateErrorEvent.FILE_UPDATE_ERROR,
_statusFile);
this.updater.addEventListener(StatusFileUpdateEvent.FILE_UPDATE_STATUS,
_statusFileUpdate);
this.updater.addEventListener(StatusUpdateErrorEvent.UPDATE_ERROR,
_updateError);
this.updater.addEventListener(StatusUpdateEvent.UPDATE_STATUS,
_updateStatus);
this.updater.addEventListener(UpdateEvent.BEFORE_INSTALL,
_beforeInstall);
this.updater.addEventListener(UpdateEvent.CHECK_FOR_UPDATE,
_checkForUpdate);
this.updater.addEventListener(UpdateEvent.DOWNLOAD_COMPLETE,
_donwloadcomplete);
this.updater.addEventListener(UpdateEvent.DOWNLOAD_START,
_donwloadStart);
this.updater.addEventListener(UpdateEvent.INITIALIZED,
_updateInitialized);
try {
this.updater.initialize();
} catch (e:Error) {
this._logger.debug(ObjectUtil.toString(e));
}
this._logger.debug(ObjectUtil.toString(this.updater));
}
}
protected function _updateInitialized(event:UpdateEvent):void
{
this._logger.debug("UpdateEvent.INITIALIZED");
}
protected function _donwloadStart(event:UpdateEvent):void
{
this._logger.debug("UpdateEvent.DOWNLOAD_START");
}
protected function _donwloadcomplete(event:UpdateEvent):void
{
this._logger.debug("UpdateEvent.DOWNLOAD_COMPLETE");
}
protected function _checkForUpdate(event:UpdateEvent):void
{
this._logger.debug("UpdateEvent.CHECK_FOR_UPDATE");
}
protected function _beforeInstall(event:UpdateEvent):void
{
this._logger.debug("UpdateEvent.BEFORE_INSTALL");
}
protected function _updateStatus(event:StatusUpdateEvent):void
{
this._logger.debug("StatusUpdateEvent");
}
protected function _updateError(event:StatusUpdateErrorEvent):void
{
this._logger.debug("StatusUpdateErrorEvent");
}
protected function _statusFileUpdate(event:StatusFileUpdateEvent):void
{
this._logger.debug("StatusFileUpdateEvent");
}
protected function _statusFile(event:StatusFileUpdateErrorEvent):void
{
this._logger.debug("StatusFileUpdateErrorEvent");
}
protected function _progress(event:ProgressEvent):void
{
this._logger.debug("ProgressEvent");
}
protected function _error(event:ErrorEvent):void
{
this._logger.debug("ErrorEvent");
}
protected function _download(event:DownloadErrorEvent):void
{
this._logger.debug("DownloadErrorEvent");
}
[flexcoders] Receiving AIR LocalConnection Slows App
Hi, I'm working through a really strange issue with my Flex 4 AIR app. I've lost days of sleep, hair, and numerous brain cells trying to get to the source of the issue with no luck. The scenario is as follows: - AIR app with initialized receiving and sending localConnection objects. - Browser with an initialized receiving and sending localConnection objects. - The AIR app receiving localConnection object is triggered by the browser, resulting in a new instance of a spark window. - Form elements in the window (DropDownList in particular) become _slow_. For example, to open up the dropDownList I need to click and hold for 3-5 seconds. The reason I believe that this is a issue with the AIR receiving localConnection is if I open a new instance of the spark window from the AIR app directly it works fine. As soon as I open a new instance from the receiving localConnection method, that instance slows. Also, any future instances opened (from the AIR app directly) are also slow until I restart the application. I'm looking for some tips on how to solve this issue. Or, if you have ideas how I can better troubleshoot this, that would be great too. Thanks, Mike
[flexcoders] Re: Receiving AIR LocalConnection Slows App
I'm still hopelessly plugging away at this. I've tried: - profiling the application to gain any insight into the issue - running traces throughout the window to see if it is firing differently I'm not able to see any differences between the window being instantiated via the receiving localConnection method and it being instantiated within the AIR app directly. The window is being instantiated the exact same way in both circumstances -- logic for launching it is encapsulated in a static method in the window itself. Maybe I'm jumping the gun, but I'm thinking this is a bug in AIR or Flex. I've opened the following report: http://bugs.adobe.com/jira/browse/SDK-23425 Any ideas? Thanks, Mike --- In flexcoders@yahoogroups.com, "michaelisraelcaplan" wrote: > > Hi, > > I'm working through a really strange issue with my Flex 4 AIR app. I've lost > days of sleep, hair, and numerous brain cells trying to get to the source of > the issue with no luck. The scenario is as follows: > > - AIR app with initialized receiving and sending localConnection objects. > > - Browser with an initialized receiving and sending localConnection objects. > > - The AIR app receiving localConnection object is triggered by the browser, > resulting in a new instance of a spark window. > > - Form elements in the window (DropDownList in particular) become _slow_. > For example, to open up the dropDownList I need to click and hold for 3-5 > seconds. > > > The reason I believe that this is a issue with the AIR receiving > localConnection is if I open a new instance of the spark window from the AIR > app directly it works fine. As soon as I open a new instance from the > receiving localConnection method, that instance slows. Also, any future > instances opened (from the AIR app directly) are also slow until I restart > the application. > > I'm looking for some tips on how to solve this issue. Or, if you have ideas > how I can better troubleshoot this, that would be great too. > > Thanks, > > Mike >
