topic Re: WidgetManager: Error #2036?? Neep help ASAP in ArcGIS Viewer for Flex Questions

WidgetManager: Error #2036?? Neep help ASAP

AlisonPage — Mon, 02 Apr 2012 13:56:15 GMT

Hi,

I just installed FlexViewer 2.5 last week and I was getting ChartWidget errors when I would try to do my release build. I looked over the new chart widget code and decided I wanted the one I had in version 2.4 so I replaced it. Now my release build is fine but when I open my mapping application online, I get a pop-up that simply says "WidgetManager: Error #2036". This error seems to keep any of my "preload open" widgets from opening and keeps my Chart and Elevation widgets from working. I don't see anything online about it this error... help please?? I have deadlines to meet and I don't want to have to revert to version 2.4 just to meet them.

Thanks in advance,
Alison

Re: WidgetManager: Error #2036?? Neep help ASAP

RobertScheitlin__GISP — Mon, 02 Apr 2012 14:07:32 GMT

Alison,

Unfortunately your mistake was reverting to the 2.4 Version of the chart widget. There are many time where you will not be able to mix and match widget versions and this is going to be one of them. If you put back in the 2.5 version of the chart widget you should be good to go again.

Re: WidgetManager: Error #2036?? Neep help ASAP

AlisonPage — Mon, 02 Apr 2012 14:39:11 GMT

I will try that.. please check back to this forum later today because most likely I'll be posting the original Chat Widget errors that I was getting 🙂

Thanks again Robert for always being available to help,

-Alison

Re: WidgetManager: Error #2036?? Neep help ASAP

AlisonPage — Mon, 02 Apr 2012 18:04:01 GMT

I put back the Chart widget and got the following error when I was trying to do the release build:

Encountered errors or warnings while building project ChartWidget.mxml.
ChartBrowserSkin.mxml: Attempted access of inaccessible property activeIndex through a reference with static type widgets.Chart:ChartBrowser.

It's the standard 2.5 Chart Widget - I changed nothing in the mxmls.

Help??

Thanks,
Alison

Re: WidgetManager: Error #2036?? Neep help ASAP

AlisonPage — Wed, 04 Apr 2012 13:04:11 GMT

Please help.. I'm on a deadline and I don't see anyone else online with this issue... I don't know how to fix it.
-Alison

Re: WidgetManager: Error #2036?? Neep help ASAP

RobertScheitlin__GISP — Wed, 04 Apr 2012 13:24:07 GMT

Alison,

What Version of the Adobe Flex SDK are you attempting to build against? You may have corrupted your Flash Builder project, as I can take the Flex Viewer 2.5 source code and build it with out issue.

Re: WidgetManager: Error #2036?? Neep help ASAP

AlisonPage — Thu, 05 Apr 2012 12:22:53 GMT

I'm using the 4.1SDK and the updated API.

I'll zip my project and send it to you if that helps.

THanks, Alison

Re: WidgetManager: Error #2036?? Neep help ASAP

AlisonPage — Thu, 05 Apr 2012 12:27:55 GMT

I'll also compile the viewer 2.5 completely and then add my other customizations bit by bit and see what breaks it I guess.

Thanks again for helping me. It's really appreciated because I have no one here who can help.

-Alison

Re: WidgetManager: Error #2036?? Neep help ASAP

RobertScheitlin__GISP — Thu, 05 Apr 2012 12:35:10 GMT

Alison,

Building AGS Viewer for Flex 2.5 using the Adobe SDK 4.1 and the AGS Flex API 2.5 works flawlessly for me so you must have done something to corrupt your project. Have you done a lot of work configuring it and that is why you are just trying to starting over again with a fresh/clean version of 2.5 (many times it is easier to start over then to diagnose what is wrong with the one you are using)?

Re: WidgetManager: Error #2036?? Neep help ASAP

AlisonPage — Thu, 05 Apr 2012 13:12:43 GMT

I've found out what is causing the error!! It's the ElevationProfile Widget. I started with the standard 2.5 viewer then added in widgets one by one.. as soon as I added the ElevationProfile widget, I got the ChartWidget error. I'm not sure why it's creating an error. For now, I'm just going to remove the Elevation widget. Hopefully it can be fixed though b/c I really like that widget!

-Alison

Re: WidgetManager: Error #2036?? Neep help ASAP

AlisonPage — Tue, 10 Apr 2012 16:32:53 GMT

I've found out what is causing the error!! It's the ElevationProfile Widget. I started with the standard 2.5 viewer then added in widgets one by one.. as soon as I added the ElevationProfile widget, I got the ChartWidget error. I'm not sure why it's creating an error. For now, I'm just going to remove the Elevation widget. Hopefully it can be fixed though b/c I really like that widget!

Robert, I was wrong.. because once I finished adding back all my other customizations, I got the chartwidget error again. Unfortunately, once I get the error, it doesn't seem to matter what I remove at that point, I continue to get the error and I have to scrap the whole project and start over... is there some way I can send you what I have right now and see if you can debug it?

Please let me know. My customer wants this application live come May 1st.. she wants the TOC for viewer 2.5 which is the whole reason I'm trying to upgrade. If I have to get rid of those widgets to make it work though, I don't think she's going to want that.

Again, thank you for your help.

-Alison

Re: WidgetManager: Error #2036?? Neep help ASAP

RobertScheitlin__GISP — Tue, 10 Apr 2012 16:48:39 GMT

Alison,

Attach a zip of your project and I will see when I can squeeze it in.

Re: WidgetManager: Error #2036?? Neep help ASAP

MLowry — Tue, 10 Apr 2012 17:18:47 GMT

You did add the chart .mxml to your flex Modules right? Which widget is causing the 2030 error? Is it a straight chart widget shown in the header controller or a customized version?

Re: WidgetManager: Error #2036?? Neep help ASAP

AlisonPage — Tue, 10 Apr 2012 17:56:37 GMT

I JUST FIGURED IT OUT! FINALLY!

Here is what the problem was.. the activeIndex that it was talking about.. it was looking for it in my PopUpRendererSkin.mxml file - but I realized I was using the mxml from the 2.4 API instead of the 2.5 API. Once I replaced that, it was able to build out with no problems.

So many customizations.. it hard to do upgrades.. geeez.

Thanks again soooo much!
Alison