Select to view content in your preferred language

How to remove Enhanced Splash Widget from an app in Flex Builder 3.4

1267
6
09-10-2013 04:52 AM
YasarKorkmaz
Occasional Contributor
This may sound like a dumb question but here is what is happening:

I am using this tool with Flex Builder 3.4. I have more than one applications. I installed this tool for 2 of my applications (app A and app B) by adding the line into each application's main config file and than copying and pasting the compiled version of the mysplash widget folder into each application's widgets folder. It works great.

HOWEVER, when I wanted to remove this mysplash widget from one of those two applications (from app B) by deleting the <splashpage url="widgets/mySplash/SplashWidget.swf" label="ArcGIS Viewer for Flex" config="widgets/mySplash/SplashWidget.xml"/> line from the application B's main config file and then deleting the mysplash folder from the application B's widgets folder, for some reason, every time I make any changes (unrelated to mysplash widget) to the application B in the Flex Builder and save the changes, Flex builder automatically adds the <splashpage url="widgets/mySplash/SplashWidget.swf" label="ArcGIS Viewer for Flex" config="widgets/mySplash/SplashWidget.xml"/>  line back into the app B's main config file causing the application to show an error message at start up since the mysplash folder is no longer in app B's widgets folder.

Can someone help me understand why this is happening and how can I stop the mysplash coming back to my application B's main config file every time I make a change in the Flex Builder for app B please?

Thank you,
Yas(h)ar
Tags (2)
0 Kudos
6 Replies
RobertScheitlin__GISP
MVP Emeritus
Yas(h)ar,

   I just tested your steps, following what you did and I do not see this behavior... Are you sure you are deleting the
<splashpage label="ArcGIS Viewer for Flex" config="widgets/mySplash/SplashWidget.xml" url="widgets/mySplash/SplashWidget.swf"/>
from the right config.xml file?
0 Kudos
YasarKorkmaz
Occasional Contributor
Hi Robert,
Yes I am pretty sure that I am deleting the line from the app B's main config file. After I delete it, if I don't make any changes to the app B in Flex Builder and don't save app B in Flex Builder, the mysplash line does not come back to app B's main config file and everything works fine. But if I make any changes at all to app B and save it in Flex Builder (actually I don t even need to make any changes, the behavior happens when i save the app B in flex builder without making any changes to the app too), Flex builder automatically puts that line back into the app B's main config file.
Yas(h)ar
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Yas(h)ar,

   As I mentioned I followed the steps you outlined and DO NOT get that behavior... There is nothing in the widget or app builder code that I can think of that would cache the widgets you have added into the application so that it would add back the splash. My advice would be to use Fiddler to watch and see exactly where the app is getting the config.xml from and check that that it the same file you are editing.
0 Kudos
YasarKorkmaz
Occasional Contributor
Hi Robert,

we looked at this with an ESRI tech support and he had seen it happening first hand as well.

But here is what I just did and the behavior ended. It seems like a new SplashWidget_1.xml file was created in the splash widget folder (not in the mysplash widget folder) of the app B's widgets folder. I just deleted this SplashWidget_1.xml file from the splash widget folder (I had already deleted the mysplash folder from the widgets folder before). Then I went back to Flex Builder, removed a geocoding widget from app B using the flex builder and saved the changes. The flex builder DID NOt this time put that line back into the app B's main config file :-).

I know this sounds strange but I was not the only one who had witnessed this behavior. The ESRI tech support guy had remoted in and witnessed the line coming back to the app B's main config file more than once. And like I said I just removed the SplashWidget_1.xml from the splash widget's folder and it stopped.

Yas(h)ar
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Yas(h)ar,

  Interesting... Was it the enhanced Splash widget that was coming back or was it the OTB Splash widget?
0 Kudos
YasarKorkmaz
Occasional Contributor
Yas(h)ar,

  Interesting... Was it the enhanced Splash widget that was coming back or was it the OTB Splash widget?


it was the enhanced Splash that was coming back. The SplashWidget_1.xml file was the enhanced Splash widget's xml.
0 Kudos