Auto Update X Control Instances

My LV version is 8.6.1 Developer
Are there any XControl experts out there?  Every time you make changes to the Xcontrol GUI but previously had utilized that XControl instances in 100 different VIs, is there a way to automatically force LV to update all those 100 VIs along with its GUI dimension?  Right now, I have to manually open all those 100 files then delete the old instances, drag and drop to create a new instance ....this is really annoying!

mishkin wrote:
I don't think you need an XControl expert on this one. As far as replications, XControls should behave just like every other control. If you want to make a change to the control and have it be replicated to previous instances, make a typedef or a strict typedef out of it. Otherwise, you'll have to go back and edit old instances of your controls manually...
No, I don't think we're on the same page here buddy.  You're thinking of the normal standard control but my question was xcontrol specific.  With a normal control with strict type def enabled, all your future instances will reflect all the changes.  Xcontrol doesn't have it.  What it does have, however, is when moving from xcontrol child data to child facade file using strict type def.  That's the best you will get out of using strict type def.  However, once you created an instance of that xcontrol, it becomes finalized.  If you try to right click on the new xcontrol instance, try to locate the feature "disconnect from type def" ...you won't see it.  It doesn't exist.  Whereas with a normal control instance, you will see it. 
Another interesing point too even when using a normal control, after you created a new instance but accidentally disconnect it from type def, good luck.  There is no way to reconnect them.  I thought NI should look into fixing all these quirky issues especially with all the other issues associating with xcontrol.

Similar Messages

  • Auto update typedef not working in LabVIEW 2009

    I was creating a type def for a customized button control and trying to figure out what action went with each of the 6 different picture images.  In the process, I found that the only way I could get my VI to auto-update the control was through using a strict typedef.  The auto update from typedef was selected, and the VI would be broken everytime I went to modify it until I saved and closed the control, but the control on the VI would not be auto updated.  I would have to replace the control to activate the change (similar to what I would need to do if the control was configured as a control and not a typedef)  This may be a bug that needs to be looked into, but I don't know where to make a bug report.
    I did find the solution to which picture image went to which action, the help files only explained 4 images.  I'll post what I found here just for reference.  The images are in the following order on the right click menu:
        1 2 3
        4 5 6
    With the following explanations for each:
     1. False Case
     2. True Case
     3. True-to-False Transition Case (time between mouse click and the release of the click)
     4. False-to-True Transition Case
     5. Mouse Hover Case when False
     6. Mouse Hover Case when True
    -Mike

    astromike wrote:
    Then that makes sense.  I'm currenlty only dealing with the appearance, I haven't dug into the Block Diagram on this one yet.  I was trying to get the appearance of the button to act correctly first, but I didn't have a good explanation of which image state did what.  Each time I tried to change it, I thought it would update on the Front Panel with the "auto update" checked.  At one point yesterday I did have the right images on the right states, but didn't see the change because it was only a typedef.  I'll keep it as a strict typedef and am glad to hear that it was with how little I understand these custom controls when used as a visual control.
    We definitely do not want the image traveling inside the Block Diagram.
    Here is my Nugget on Type defs. There may be something in there that can help you. At the tail end I mention default values and ways to handle them.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Recommeneded Auto Update Feature in 11.1 Grid Control

    Hi All,
    I would like inform you about New Auto Update feature in the 11.1 Grid Control Installer. This feature allows the latest recommended patches to be automatically deployed while installing a fresh 11.1 Grid control or while upgrading an existing Grid control to 11.1 version.
    These auto updates ensure that any patches required by the oracle installer or for successful installation/upgrade of the product are applied before the actual installation or upgrade process. It ensures that there are no failed installations or upgrades from known issues.
    Oracle highly recommends using this feature to ensure that any new or upgraded Enterprise Manager installation is successful
    To know more about usage and benefits of this feature Refer to :
    1. Note.1101208.1 Required Patches for Grid Control 11g (11.1.0.1.0) on Linux
    2. Note.1099123.1 Overview of the "Auto Update" Feature Available with Grid Control 11g Install/Upgrade
    3. Refer to this PDF
    4. Use Install forum to place your queries
    Note:- If you have downloaded and installed your Grid control before15th May 2010 then we recommend you to apply this Generic Agent patch 9676134 on all your target boxes. Refer to the Read-me of the patch for exact instructions. If you don't have this patch applied then you will see this patch appear in MOS recommended section for that target as well.
    This patch fixes the performance issue that is caused by Grid control 11.1 running a metric query against the v$rman_backup_job_details view on target database instances for Oracle Database 10g Release 2 (10.2.0.1) or higher. In some situations, this query might expose RDBMS bug 8434467, in which the query can run for an extended period of time, resulting in high CPU utilization.If you notice this problem, it is recommended that you apply the patches listed below, which will reduce the the frequency of the query.

    Thank you

  • CC Updater - U44M1I11 Another Instance is Running

    Seems like just last month I was struggling with this problem with CS6. Oh wait, I was:
    http://forums.adobe.com/message/5753380#5753380
    So now I'm back with CC. Installed all the programs today. Hit Update and of course Photoshop, Premiere, and Audition failed their Updates. Error this time was:
    There was an error installing this update. Please try again or contact customer support. (U44M1|11)
    I see that root spawns the Adobe Application Manager (Updater) process when I hit the Update button. Then the update fails.
    Here's the end of the log file from /Library / /  Adobe Setup Error.log
    11/08/13 13:52:02:164 | [INFO] |  | OOBE | DE |  |  |  | 11968 |
    11/08/13 13:52:02:164 | [INFO] |  | OOBE | DE |  |  |  | 11968 | Exit Code: 11 - Another instance running, Only a single instance can be run at a time.
    11/08/13 13:52:02:165 | [INFO] |  | OOBE | DE |  |  |  | 11968 | Please see specific errors for troubleshooting. For example, ERROR: DW037 ...
    What's the fix, Adobe? Don't send me to:
    http://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-updates-ccm.html
    I've already done that stuff. I'm so aggravated with this auto updater, it just doesn't work out of the box. This is a brand new 10.9 system, nothing else on it, except for CC, and it won't run it's updates after it's been installed.

    Should have waited a few more minutes before posting the above issue. I fixed it, but the workaround is pretty poor. Adobe, you have problems with the root user spawning the updater's processes. Simple as that.
    Here's my fix:
    Enable the root user and give it a password in the Directory Utility (Users Groups/Login Options/Network Account Server/Open Directory Utility)
    Curse Adobe for forcing you to enable the root user and thus provide another attack vector on your machine
    Open Terminal
    su to become the root user
    Navigate to /Applications/Adobe Photoshop CC/Adobe Photoshop CC.app/Contents/MacOS
    Run Photoshop as root by using ./Adobe Photoshop CC
    Photoshop yelled at me for a password to run something when it started up, I ignored it
    Use the Update... option in the Help menu.
    Note in Activity Manager that this has been spawned by Root
    Check off the boxes of programs you want to update, let the updater run. You will have to close out of Photoshop and then quit it by hitting Control C in your Terminal window
    You may also have to go into Activity Manager and Force Quit the logtranspot2 process.
    Wait for the update to complete
    Quit Terminal
    Quit and re-open the Creative Cloud app and verify all the programs show as "Up to Date"
    Disable the root user
    Curse Adobe for forcing you to do this every time you want to update your Creative Cloud programs. It's not very convienent.
    So anyway, there's your fix. Hope it saves someone else a few hours of aggravation.

  • Lost sound QT X after auto update

    I just got this MacBook with Lion 0.7.5 and I had sound.  It did an auto update and I lost audio and video on a particular website.  I have a/v on youtube and I have audio on cd.  Something is wrong.  Can someone help?  I'm trying to learn Apple, I'm more MS familiar.  Thanks, breeze

    Breeze, try taking the QuickTime 7.6.6 download. It's the older 32-bit player that can work with almost every audio/video codec available - and many of the files used on various websites can be made to work if you get the correct codec packs.
    Right now there is a whole change happening and one of the updates you took may have flipped a settings switch somewhere.. DO be mindful that Mavericks 10.9 IS FREE and if you do take that upgrade, you will absolutely WANT to re-install the QT7.6.6 asnd install all the codecs again, as 10.9 is now stepped up on the video to 64-bit processing and it's also embedded the playback function further down into the operating system, closer to the hardware level.. Ugh.
    Here's the list to try, I've made this for the people with video issues in Mavericks, but all these options work well enough on every OS as far back as Tiger Mac OS X 10.4 (I have this installation package on one of my machines)
    Start with QT 7.6.6. - http://support.apple.com/kb/DL923
    Get Perian, and install it. - http://perian.org
    then VLC, - http://videolan.org
    DivX - http://divx.com - and the
    Flip4Mac package from Telestream - http://www.telestream.net/flip4mac/
    A52/AC3 downloader: https://www.macupdate.com/app/mac/21875/a52codec - In this installer package there is an audio A52Codec.component. DO NOT USE IT! Throw it out and use the one that is linked below.
    This is what I've put into my system and so far I've gotten every file to run fine, even my oldest videos.
    These are codecs you should see.
    In System/Library/QuickTime
         AppleIntermediateCodec.component
         AppleMPEG2Codec.component* (*optional if you've bought it)
         DivX Decoder.component
         Flip4Mac WMV Advanced.component
         Flip4Mac WMV Export.component
         Flip4Mac WMV Import.component
    In your Home/Library/QuickTime/
         AC3MovieImport.component (you may or may not want this component, in some instances it causes conflicts. In my system, it doesn't. Who knows why? I don't.)
         Perian.component
    For AC3 sound that is in most .mkv files, you need the A52Codec.component, this is the one you want, here:https://dl.dropboxusercontent.com/u/34821905/A52Codec.component.zip - unzip the file and put the component into the System/Library/Audio/Plug-ins/Components
    Perian is a System Prefences control panel and set it so it doesn't check for updates, since it is no longer in development. (but still works perfectly)
    Good luck!

  • Client Auto-Update questions

    We just updated our Dev system to SP5 with Patch 2, but the clients are not updating automatically.
    I have checked that the Client and Admin boxes are checked for auto-update and can see nowhere else that this can be done.
    I double-checked with the Master Install guide, and this appears to be the only thing that I need to do to make it work.
    The clients are currently at 502, and they should now be 506.
    Also, is this controlled by the files in C:\BPC\Websrvr\Web\Installation?
    I have checked the live server (BPC 5.1 SP3) and the Dev server (BPC 5.1 SP5r2)
    Both of them have EverestClient.exe and EverestAdmin.exe with version number 12.0.0.49974
    Does that seem right?  I would have expected an increment in version number.
    Has anyone else seen this, and can you offer any advice?
    Thanks
    Craig
    Edited by: Craig Aucott on Feb 23, 2009 9:46 AM

    Here is an extract from the note:
    It does not say about the Patch! sorry...
    the note is 1269662
    Summary
    Symptom
    The Client Auto Update feature does not work in 5.1 SP5.
    Other terms
    auto, update, client, upgrade, install
    Reason and Prerequisites
    This is due to unintended consequences of fixing IM 3569686 issue in SP5.
    Solution
    Remove the '<remove name="Documentation"/>' node from the web.config file located in the x:\bpc\websrvr\web directory and save.
    Once all clients have been updated, add the node back to the file.
    The node is found in the following section:
    <globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
      <webServices>
           <protocols>
                <add name="HttpSoap"/>
                <add name="HttpGet"/>
                <add name="HttpPost"/>
                <remove name="Documentation"/>
            </protocols>
      </webServices>
    Header Data
    Release Status:     Released for Customer
    Released on:     25.11.2008  19:51:41
    Master Language:     English
    Priority:     Correction with high priority
    Category:     Program error
    Primary Component:     EPM-BPC-MS-SVM-OTH Other
    Hope this helped
    Bye

  • How to disable yum auto-update in OL6

    Hello,
    What is the correct procedure to disable yum auto-updates?
    The "yum-updatesd" daemon that existed in OL 5 does no longer exist in OL 6.
    I found out that the "PackageKit Update Applet" seems to be responsible for running the auto-update. It can be enabled or disabled in the new Preferences/Startup Applications control panel. There is also the "gpk-prefs" control panel to set the update interval to "never". However, both control panels work on a per-user/login basis and cannot be used to disable yum auto-update system-wide.
    Finally I found /etc/PackageKit/PackageKit.conf, which has a DefaultBackend parameter, but I don't know what I should put there.
    Is there here a way, to disable the yum auto-update system-wide without uninstalling PackageKit?
    I already checked the documentation at http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-PackageKit.html but it was not helpful.
    Thanks!

    The actuall problem I'm trying to fix is the following error:
    <pre>
    Another app is currently holding the yum lock; waiting for it to exit...
    The other application is: PackageKit
    Memory : 45 M RSS (357 MB VSZ)
    Started: Tue Jul 10 09:27:04 2012 - 04:09 ago
    State : Sleeping, pid: 2317
    </pre>
    The above error can happen if you have an active Gnome session and e.g. connect as root using ssh session and try to use yum.
    I may have found a way now to disable the automatic system updates, however, I don't know if this is the proper solution since I cannot find any information about it.
    I modified */etc/PackageKit/PackageKit.conf* and changed:
    <pre>
    DefaultBackend=yum -> DefaultBackend=nobackend
    </pre>
    It requires a re-login of your Gnome X session to take affect.
    Then Administration/Software update does no longer scan for updates, and apparently no longer lock yum at the system level. At least the problem seems to be fixed globally that way.
    I will mark this question as answered, but any ideas are still welcome.
    Thanks!
    Btw, here is a link to previous older thread to disable it on a per-user basis:
    Disable PackageKit Update Applet

  • Auto update of events in albums

    Hello! My question is this . . .
    If I create a new album, and then add an event, will the album dynamically update if I add/remove photos to the event?
    Thanks!
    Michael

    Thanks Larry! I think I get it now. Standard albums won't auto update (not dynamic), but if I create a Smart Album ("Travel" for instance), with the event as a criteria (for example, all events that contain the word "vacation"), and if I add photos to any of my "vacation" events, those photos will appear in my "Travel" album. Does this sound right?
    Thanks!
    Michael

  • How to auto update a section on all pages.

    Hi,
    I have a section on the right hand side of a website I'm developing containing txt and it's controlled by CSS which also appears on all the other pages, so what I want to be able to do is when I add a new bit of text to it on one page it will auto update with the new txt on all the other pages to save me copying and pasting the same bit of txt on all the pages.
    Hope that made sense and hope someone can help.
    Thanks

    You can use Dreamweaver Templates or use serverside include.   (SSI)
    Using the template function within Dreamweaver is a good way to go if it's a small site . .
    For larger sites then serverside includes would be more practical and earlier for maintenance purposes.
    Templates:
    You create a master template page, you declare which areas will be the same for every page, (non-editable regions)  and then declare an area that will change on every page (the content area) , these are editable regions.
    Once you create the template and save it, you are then able to create 'child' pages from this template  - as many as you like  :-)  If you every need to make a change to the menu or the footer or the header, change it in the master template, save it and the changes will flow through to the child pages created from the template.
    Using DW Templates:
    http://www.adobe.com/devnet/dreamweaver/templates.html
    http://www.adobe.com/devnet/dreamweaver/articles/dw_templates.html
    The other option is to use Server Side Includes (SSI)
    A bit more about SSIs here:
    http://help.adobe.com/en_US/Dreamweaver/10.0_Using/WSc78c5058ca073340dcda9110b1f 693f21-7b6ca.html
    http://bignosebird.com/ssi.shtml
    One major difference between using Templates and SSI?
    When you make a change to a template page, you will need to re-upload all the pages to the server that were changed - may become very tedious if it is a very large site.
    With using SSI, you make a change to one file and only have to upload the one file and all pages on the server will be update accordingly.
    When to use Templates, Library Items & SSIs -
    http://www.adobe.com/devnet/dreamweaver/articles/ssi_lbi_template.html
    Nadia
    Adobe® Community Expert : Dreamweaver
    Unique CSS Templates | Tutorials | SEO Articles
    http://www.DreamweaverResources.com
    Web Design & Development
    http://www.perrelink.com.au
    http://twitter.com/nadiap

  • Air Auto Update Error -- Flash Builder Burrito.

    This is my first attempt at this, so I may be missing something simple.
    I'm not having any luck getting an Air app to automatically update.
    If I manually go to  http://localhost/air1/air1.air and redownload the file I will get a popup that asks if I want to update the app, but when I say ok I get this error.
    "There was an error checking for updates. Error# 16816"
    I haven't found a reason yet,
    Any ideas?
    update.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
      <version>2.0</version>
      <url>http://localhost/air1/air1.air</url>
      <description>1.0 - First version</description>
    </update>
    file -- air1.mxml
    <?xml version="1.0" encoding="utf-8"?>
    <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                           xmlns:s="library://ns.adobe.com/flex/spark"
                           xmlns:mx="library://ns.adobe.com/flex/mx"
                           applicationComplete="init()">
        <fx:Declarations>
            <!-- Place non-visual elements (e.g., services, value objects) here -->
        </fx:Declarations>
        <fx:Script>
            <![CDATA[
                import air.update.events.UpdateEvent;
                import air.update.ApplicationUpdaterUI;
                import mx.controls.Alert;
                protected var appUpdater:ApplicationUpdaterUI = new ApplicationUpdaterUI(); // Used for auto-update
                protected function init():void
                    // Check for update
                    this.checkUpdate();
                    Alert.show("checking update");
                // This function is triggered when the application finished loading.
                // Initialize appUpdater and set some properties
                protected function checkUpdate():void
                    // set the URL for the update.xml file
                    appUpdater.updateURL = "http://localhost/air1/update.xml";
                    appUpdater.addEventListener(UpdateEvent.INITIALIZED, onUpdate);
                    appUpdater.addEventListener(ErrorEvent.ERROR, onUpdaterError);
                    // Hide the dialog asking for permission for checking for a new update.
                    // If you want to see it just leave the default value (or set true).
                    appUpdater.isCheckForUpdateVisible = true;
                    appUpdater.initialize();
                // Handler function triggered by the ApplicationUpdater.initialize.
                // The updater was initialized and it is ready to take commands.
                protected function onUpdate(event:UpdateEvent):void
                    // start the process of checking for a new update and to install
                    appUpdater.checkNow();
                // Handler function for error events triggered by the ApplicationUpdater.initialize
                protected function onUpdaterError(event:ErrorEvent):void
                    Alert.show(event.toString());
            ]]>
        </fx:Script>
        <s:Button x="47" y="55" label="Button"/>
        <mx:ColorPicker x="61" y="119"/>
        <s:ComboBox x="77" y="216"/>
        <s:ComboBox x="77" y="185"/>
        <s:ComboBox x="77" y="154"/>
    </s:WindowedApplication>
    file  -- air1-app.xml
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/2.5">
    <!-- Adobe AIR Application Descriptor File Template.
        Specifies parameters for identifying, installing, and launching AIR applications.
        xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.5
                The last segment of the namespace specifies the version
                of the AIR runtime required for this application to run.
        minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                the application. Optional.
    -->
        <!-- A universally unique application identifier. Must be unique across all AIR applications.
        Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
        <id>air1</id>
        <!-- Used as the filename for the application. Required. -->
        <filename>air1</filename>
        <!-- The name that is displayed in the AIR application installer.
        May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <name>air1</name>
        <!-- A string value of the format <0-999>.<0-999>.<0-999> that represents application version which can be used to check for application upgrade.
        Values can also be 1-part or 2-part. It is not necessary to have a 3-part value.
        An updated version of application must have a versionNumber value higher than the previous version. Required for namespace >= 2.5 . -->
        <versionNumber>2.0.0</versionNumber>
        <!-- A string value (such as "v1", "2.5", or "Alpha 1") that represents the version of the application, as it should be shown to users. Optional. -->
        <!-- <versionLabel></versionLabel> -->
        <!-- Description, displayed in the AIR application installer.
        May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <!-- <description></description> -->
        <!-- Copyright information. Optional -->
        <!-- <copyright></copyright> -->
        <!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
        <!-- <publisherID></publisherID> -->
        <!-- Settings for the application's initial window. Required. -->
        <initialWindow>
            <!-- The main SWF or HTML file of the application. Required. -->
            <!-- Note: In Flash Builder, the SWF reference is set automatically. -->
            <content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
            <!-- The title of the main window. Optional. -->
            <!-- <title></title> -->
            <!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
            <!-- <systemChrome></systemChrome> -->
            <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
            <!-- <transparent></transparent> -->
            <!-- Whether the window is initially visible. Optional. Default false. -->
            <!-- <visible></visible> -->
            <!-- Whether the user can minimize the window. Optional. Default true. -->
            <!-- <minimizable></minimizable> -->
            <!-- Whether the user can maximize the window. Optional. Default true. -->
            <!-- <maximizable></maximizable> -->
            <!-- Whether the user can resize the window. Optional. Default true. -->
            <!-- <resizable></resizable> -->
            <!-- The window's initial width in pixels. Optional. -->
            <!-- <width></width> -->
            <!-- The window's initial height in pixels. Optional. -->
            <!-- <height></height> -->
            <!-- The window's initial x position. Optional. -->
            <!-- <x></x> -->
            <!-- The window's initial y position. Optional. -->
            <!-- <y></y> -->
            <!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
            <!-- <minSize></minSize> -->
            <!-- The window's initial maximum size, specified as a width/height pair in pixels, such as "1600 1200". Optional. -->
            <!-- <maxSize></maxSize> -->
        <autoOrients>false</autoOrients>
        <fullScreen>false</fullScreen>
        <visible>false</visible>
      </initialWindow>
        <!-- We recommend omitting the supportedProfiles element, -->
        <!-- which in turn permits your application to be deployed to all -->
        <!-- devices supported by AIR. If you wish to restrict deployment -->
        <!-- (i.e., to only mobile devices) then add this element and list -->
        <!-- only the profiles which your application does support. -->
        <!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
        <!-- The subpath of the standard default installation location to use. Optional. -->
        <!-- <installFolder></installFolder> -->
        <!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
        <!-- <programMenuFolder></programMenuFolder> -->
        <!-- The icon the system uses for the application. For at least one resolution,
        specify the path to a PNG file included in the AIR package. Optional. -->
        <!-- <icon>
            <image16x16></image16x16>
            <image32x32></image32x32>
            <image36x36></image36x36>
            <image48x48></image48x48>
            <image72x72></image72x72>
            <image128x128></image128x128>
        </icon> -->
        <!-- Whether the application handles the update when a user double-clicks an update version
        of the AIR file (true), or the default AIR application installer handles the update (false).
        Optional. Default false. -->
        <!-- <customUpdateUI></customUpdateUI> -->
        <!-- Whether the application can be launched when the user clicks a link in a web browser.
        Optional. Default false. -->
        <!-- <allowBrowserInvocation></allowBrowserInvocation> -->
        <!-- Listing of file types for which the application can register. Optional. -->
        <!-- <fileTypes> -->
            <!-- Defines one file type. Optional. -->
            <!-- <fileType> -->
                <!-- The name that the system displays for the registered file type. Required. -->
                <!-- <name></name> -->
                <!-- The extension to register. Required. -->
                <!-- <extension></extension> -->
                <!-- The description of the file type. Optional. -->
                <!-- <description></description> -->
                <!-- The MIME content type. -->
                <!-- <contentType></contentType> -->
                <!-- The icon to display for the file type. Optional. -->
                <!-- <icon>
                    <image16x16></image16x16>
                    <image32x32></image32x32>
                    <image48x48></image48x48>
                    <image128x128></image128x128>
                </icon> -->
            <!-- </fileType> -->
        <!-- </fileTypes> -->
        <!-- Specify Android specific tags that get passed to AndroidManifest.xml file. -->
        <!--<android>
            <manifestAdditions>
            <![CDATA[
                <manifest android:installLocation="auto">
                    <uses-permission android:name="android.permission.INTERNET"/>
                    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
                    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
                    <uses-configuration android:reqFiveWayNav="true"/>
                    <supports-screens android:normalScreens="true"/>
                    <uses-feature android:required="true" android:name="android.hardware.touchscreen.multitouch"/>
                    <application android:enabled="true">
                        <activity android:excludeFromRecents="false">
                            <intent-filter>
                                <action android:name="android.intent.action.MAIN"/>
                                <category android:name="android.intent.category.LAUNCHER"/>
                            </intent-filter>
                        </activity>
                    </application>
                </manifest>
            ]]>
            </manifestAdditions>
        </android> -->
        <!-- End of the schema for adding the android specific tags in AndroidManifest.xml file -->
    </application>

    This appears to be a Flex question. Please try posting to the Flex forums here http://forums.adobe.com/community/flex/flex_general_discussion for better response.

  • Why does turning off auto updates turn them on?

    I have been trying to stop the auto update of Flash player for months - even went so far as to totally uninstall, remove all traces, then install fresh with the "do not auto update" setting. It still gives me pop-ups. Browsing the 'net I saw an article that made me think it might be related to Shockwave. Shockwave has NEVER asked me to update but, silly me, I unchecked it anyway.
    And now it is on and attempting to auto update.
    So, I'm left with two products that will not obey their settings.
    Please advise.

    i MonH,
    Unless someone deleted the file, it should exist on your system.  If you're on a 32-bit OS, the file will be in C:\Windows\System32\Macromed\Flash.  If you're on a 64-bit OS, the file will be in C:\Windows\SysWOW64\Macromed\Flash.  You can edit the file manually, or edit the update settings in the Flash Player Settings Manager, which may be easier. 
    To launch the Settings Manager, either navigate to the Control Panel and select the Flash Player icon, or launch a non-Chrome browser and view Flash content, then right-click on the content to display the Flash Player context menu.  Select Global Settings.
    When the Settings Manager displays, navigate to the Advanced tab.
    Click the Change Update Settings button
    Select the Never check for updates (not recommended) radio button
    Your update option has been set
    Viewing the mms.cfg file after making the updates, it should contain the following:
         AutoUpdateDisable=1
         SilentAutoUpdateEnable=0
    AutoUpdateDisable=1 is what disables the updates (background and notification) completely.
    Note that whenever you uninstall Flash Player the update settings are reset to the default setting (AutoUpdateDisable=0).  You'll need to be sure to select Never check for updates (not recommended) when you install Flash Player again.
    Maria

  • We are trying to package our iTunes Windows and we can't stop the auto update feature.  How can we do this?

    We have consultants here packaging many of our Apps for deployment with Windows 7.  We cannot find a way to turn off the auto update feature within iTunes for Windows.  Has someone been successful in packaging iTunes for Windows and NOT do the auto update piece?

    The Apple advice revolves around the editing the registry:
    Windows OS Managed Client: How to manage iTunes control features
    ... but it's beyond my competence to advise how to work that particular registry edit into a deployment, I'm afraid.

  • How do I stop auto update of date/time

    Hi,
    I'm starting to despair, a while ago I stupidly clicked on auto update/time on a letter I was working on, it seemed like a good idea at the time. But now whenever I open any letter the date is automatically updated which is a major problem as I am losing the references to when I actually wrote and therefore sent these letters. I'm too scared to open letters now because I'll lose this important piece of information.
    Any help appreciated!
    Thanks
    Nathalie

    Next time, don't use the Pages 's insert date_time feature.
    Use the one delivered in the free WordService from Devon Technologies.
    It always inserts a fixed date_time.
    But I have wondering about your problem.
    The Pages User Guide states:
    • To add and format the date and time, place the insertion point where you want the value to appear, and then choose Insert > Date & Time.
    To change the date and time format, Control-click the date and time value, choose Edit Date & Time, and then choose a date and time format from the pop-up menu. *If you want the document to always show the current date and time, select “Automatically update on open.”*
    Which, if I understand well means that the default setting is that the inserted date_time is a frozen (fixed) one.
    Yvan KOENIG (VALLAURIS, France) mardi 30 mars 2010 16:29:17

  • Can't Stop Auto-Update

    When I connect my BB Bold and startDesktop Manager, it automatically launches into auto-update: "Checking for device application updates...". If I click on "Cancel", it ignores me, but it doesn't hang. It eventually comes up with the message: "Updated versions... are available.. Blackberry 4.6 Core Applications". I am using 4.7 - So that doesn't make sense.
    I have tried to disable Auto-Update by clicking on "Check for Updates" and un-checking "Check for Updates automatically". But that makes no difference. I have looked for and renamed Vendor.xml (per some suggestions) but cannot find a Web.xml file. Renaming Vendor.xml to _Vendor.xml (so I can undo the change) makes no difference.
    Any more suggestions?
    Sean

    First off, your device does use the 4.6 software, even if the version of BlackBerry Desktop Manager is 4.7.  There is no 4.7 OS for the Bold.
    Second, the reason you're seeing this message is likely because you have the device software installed on your computer.  Go to your computer's Control Panel, then Uninstall Programs (in Vista, it's under Programs & Features in Classic View).  Remove any BlackBerry Device software you see (not the Desktop Manager, just the device software).  Once this is done, restart your computer.
    This should resolve the issue. 
    If you want to thank someone for their comment, do so by clicking the Thumbs Up icon.
    If your issue is resolved, don't forget to click the Solution button on the resolution!

  • Disable JRE Auto update in Vista for all users?

    I feel like a complete idiot that I can't figure this out, but it's either so obvious I'm overlooking it, or I just plain can't figure it out, so I'm hoping someone here can help.
    We have not yet been able to figure out how to simply disabled the Auto Update option when installing JRE under Vista, so it will never check for updates, no matter what user is logged into a pc. I've just installed the newest version 1.6.0_05-b13, but get the same results.
    Basically, we are creating a "base clone image" of a Vista workstation and we need the auto update feature of the JRE to be disabled so it doesn't check for updates. When a new user logs into the pc, we want them to 'inherit' this setting from the default user profile, or we simply want a 'global' setting on the pc that stops all JAVA update checks from occuring. But even though there are multiple registry keys that 'look' like they control the auto update function, no matter how we set them the update option still shows it is enabled when you open the JAVA control panel.
    We have 2 basic problems:
    - When a standard user runs the JAVA Control Panel applet and they select the 'Update' tab, the option to "uncheck" autoupdates is "grayed out". If we make the user a local administrator, then it is not grayed out anymore and they can set the option. Problem is, we have thousands of users and none of them are local administrators, hence the problem of getting it to already be defaulted to not check for updates. How do we get the update checkbox to NOT be grayed out for a NON-administrator?
    - How do we set the 'global' (or default) option to disable the auto update checkbox for ALL users? No matter what we try, when a new user logs in, the auto update feature is still enabled after their initial profile is generated from the first time login.
    I was able to figure out if I change the "EnableJavaUpdate" value in the below registry key, it will "remove" the Update tab from the JAVA Control Panel. But does the simply remove the tab? Or does it remove the tab AND disable auto updates for ALL users on the computer?
    HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy
    I've sent multiple emails to Sun asking for help on what should be a simple thing to do, but have never received a reply from them.
    Keith Hemmelman

    Thank you for the reply. I apologize for not getting back here sooner.
    We actually already use a deployment.properties file located under the Default User profile on our Vista setup. It's located under the "C:\Users\Default\AppData\LocalLow\Sun\Java\Deployment" folder. This file does get copied over to a new user profile when a new person logs in. This is what we want since we have set things like the maximum cache size and temporary file location.
    The problem though is there is no setting that disables the automatic update check within this file. The best I can figure out is that for some reason under the Vista environment, the auto update setting is controlled in the registry at: HKEY_CURRENT_USER\Software\JavaSoft\Java Update\Policy
    There is a REG_BINARY key there that appears to control this option. It is named "EnableAutoUpdateCheck". The problem is that the value of this key is "several" characters long and it is "different" from one user to the next. I tried disabling auto update under the Java Control Panel and then copied the value of this key into the same aread of the Default User hive but when a new user logs in, it ignores that setting and auto update is still enabled. I also tried using a simple "0" to disable the autoupdate or a "1" to enable it for this key, but it doesn't work either. (This is very frustrating why there isn't a simple 1 or 0 setting to turn the auto update setting on/off.)
    We had no problem getting this to work under XP. Basically we didn't have to do anything special in XP. We simply created a temporary user account and made all the settings we wanted and then copied that profile over to our Default User profile and the Java autoupdate setting under the Java Control Panel was disabled for all new users. We did the same thing under Vista, but the auto update setting was ignored and re-enabled for all new users.
    I read through the settings for the deployment.properties file located at the below link, but there is nothing there to control the auto update setting.
    http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/properties.html
    Thus, we can't get the auto update setting to be disabled in the default user profile so it will in turn be disabled for all new users that log into the computer. This is extremely frustrating.
    The other equally frustrating problem we have run into under the Vista environment is that when you run the Java Control Panel, the option to disable the auto update check is "grayed out" and the user can't uncheck this option to disable auto update. We have found you must be an administrator before this option is no longer grayed out. Since none of our thousands of users are admins, this is also a problem for us. (This option works fine for a standard user if you are on a XP machine though. It's just Vista where things have changed.)
    I've sent repeated emails to Sun in the past asking for help, but they never replied.
    Keith

Maybe you are looking for

  • Memory Juggle - Not all chips are recognized.

    I have a MacPro. It is the base model 2.8 quad core with two 1GB 800Mhz chips in it. I added four 2GB chips to the machine (3rd party) Of course what i am doing/describing is paired per both pull-out memory cards. I moved the Apple 1GB chips to the 3

  • Report/Process Issue

    Getting close to finishing this project but ran into a new issue. When the user performs a search, a report (non-interactive) is generated and displays a Cart icon if the item is In; this is also a link to add the item to your cart for ordering. The

  • Desktop AIR app debug build running from cache?

    I'm new to flash builder (using 4.5 for os x) and I've been working on a desktop AIR app for the last week.  I've been running into a strange issue when deugging my app.  Every once and a while (maybe 4-5 times a day) after I make changes to my code

  • Installer problems ?? frozen and cant shut down :(

    installer problems ?? frozen and cant shut down

  • Where can I get a copy of iTunes 5 and how do I keep my purchased music?

    Hi all: I am using iTunes 5 (5.0.0.35) and want to reinstall it as I get the following error message from the iTunes Setup Assistant when iTunes starts up: "Warning! The registry settings used by the iTunes drivers for importing and burning CDs and D