Select to view content in your preferred language

WidgetManager: Error #2036?? Neep help ASAP

1819
13
04-02-2012 06:56 AM
AlisonPage
Regular Contributor
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
Tags (2)
0 Kudos
13 Replies
AlisonPage
Regular Contributor
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
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Alison,

   Attach a zip of your project and I will see when I can squeeze it in.
0 Kudos
MLowry
by
Frequent Contributor
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?
0 Kudos
AlisonPage
Regular Contributor
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
0 Kudos