State of Transitions Bug

Need help.  I played with transitions recently.  Specifically the transition from one State to another.  So far, I have concluded that bland is on the only effect which is not buggy.  I can't travel more than any other effect.  For some reason any movement works the first time, but if you were to return to the location of what you were the movement gets completely become misaligned.  I've included an example below.

<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
               xmlns:s="library://ns.adobe.com/flex/spark" 
               xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="800" minHeight="800">
     
     <s:states>
          <s:State name="state1"/>
          <s:State name="state2"/>
     </s:states>
     
     <s:transitions>
          <s:Transition fromState="state1" toState="state2">
               <s:Sequence>
                    <s:Parallel target="{panel1}">
                         <s:AddAction/>
                         <s:Fade/>
                         <s:Move xTo="800" xFrom="262.5"/>
                    </s:Parallel>
                    <s:RemoveAction target="{panel1}"/>
                    <s:Parallel target="{panel2}">
                         <s:AddAction/>
                         <s:Fade/>
                         <s:Move xTo="262.5" xFrom="800"/>
                    </s:Parallel>
                    
               </s:Sequence>
          </s:Transition>
          <s:Transition fromState="state2" toState="state1">
               <s:Sequence>
                    <s:Parallel target="{panel2}">
                         <s:AddAction/>
                         <s:Fade/>
                         <s:Move xFrom="262.5" xTo="800"/>
                    </s:Parallel>
                    <s:RemoveAction target="{panel2}"/>
                    <s:Parallel target="{panel1}">
                         <s:AddAction/>
                         <s:Fade/>
                         <s:Move xFrom="800" xTo="262.5"/>
                    </s:Parallel>
               </s:Sequence>
          </s:Transition>
     </s:transitions>
     
     <s:Panel id="panel1" 
              title="Panel 1" textAlign="center"
              width="275" height="170" includeIn="state1" cornerRadius="10" x="262.5" y="315">
          <s:Button id="next1" label="Next"
                    horizontalCenter="0" bottom="5" click="currentState='state2'"/>
     </s:Panel>
     
     <s:Panel id="panel2"
              title="Panel 2" textAlign="center"
              width="275" height="170" includeIn="state2" cornerRadius="10" x="262.5" y="315">
          <s:Button id="next2" label="Next"
                    horizontalCenter="0" bottom="5" click="currentState='state1'"/>
     </s:Panel>
     
</s:Application>

If you run the above code, you will see that the original animation works perfectly.  However, when you click on the next button to return to the State 1 the animation ends and then moves the Panel 1 off the screen.  No idea why this is happening.  Any ideas?  I use the bad transition?

I think that you run into a situation where States and the transitions are fighting for the position should be, here is an example of reduction:

http://ns.Adobe.com/MXML/2009.
xmlns:s = "library://ns.adobe.com/flex/spark" >
   
   
       
       
   

   
   
       
           
       

   

   
   
       
       
   

   
   
   

This is because the effect moves the Panel to 800 as his, but the transition ends and x is then defined on its state2 value (which is 262.5).

In general when you set transitions you should not define all the properties on the effects (like xFrom/xTo etc.) because they can conflict with the values that are specified in the States.  In the following code snippet, you shouldn't do this:


       
           
       

   

...
   

But on the contrary must define the position of every State and does not give the move effect any additional information:


       
           
       

   

...
   

As a solution for your original example, you can get the behavior you want by making a very subtle change is to set x.state1, x.state2 of the values for the two components:

http://ns.Adobe.com/MXML/2009.
xmlns:s = "library://ns.adobe.com/flex/spark".
xmlns:MX = "library://ns.adobe.com/flex/mx" minWidth = "800" minHeight = "800" >
   
   
       
       
   

   
   
       
           
               
                   
                   
                   
               


               
               
                   

                   
                   
               
               
           
       
       
           
               
                   
                   
                   
               

               
               
                   
                   
                   
               

           

       

   
   
   
title = "Group 1" textAlign = "center".
"width ="275"height ="170"includeIn ="state1"cornerRadius ="10"x.state1 ="262.5"x.state2 =" 800 "y ="315">
       
horizontalCenter = "0" low = click on '5' = "currentState = 'state2'" / > "
   
   
   
title = "Group 2" textAlign = "center".
"width ="275"height ="170"includeIn ="state2"cornerRadius ="10"x.state1 ="800"x.state2 =" 262.5 "y ="315">
       
horizontalCenter = "0" low = click on '5' = "currentState ="state1"" / > "
   
   

Tags: Flex

Similar Questions

  • Widget slideshow active State does not, Bug?

    I tried the widget "slide show: thumbnails ' multiple times with different options and can not get the State of the assets of the miniatures of this widget to work at all.

    I'm doing something wrong? Is there a bug in the system? When will this fix if this is a bug?

    It seems that it is indeed a bug with the miniatures of the active state, thank you for reporting it. I produced it, and we have to look into it for future versions.

    For an immediate solution, you can use composition instead of slide widgets (although widgets of composition are much more free-form, and the tiles will have to be placed manually).

  • &amp; APPLICATION. in State of IR: Bug or my mistake

    APEX 4.0.2.00.07
    I have an interactive report, it has the status: "& REQUEST." = "SEARCH".
    (FIND is a request button)
    If I try to use an 'action', as "select columns", it seems doing nothing pending.
    If I change the status of the report so that it checks a REQUEST page and POINT instead of. all the works!
    Maybe a bug in the APPLICATION of the interactive report audit &. or I made a mistake?
    Thank you
    Stefano Corradi

    (I use the condition so that when I press tab it show only not the report selection, he has dealt with when I press on FIND)

    Hi Stefano,

    Take a look at http://insum-apex.blogspot.com/2010/05/apex-interactive-reports-and-request.html
    It might be a good solution for you.

    Concerning
    Patrick
    -----------
    My Blog: http://www.inside-oracle-apex.com
    APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins
    Twitter: http://www.twitter.com/patrickwolf

  • The State of Transition (VM_STATE_ON-&gt; VM_STATE_CREATE_SNAPSHOT) not allowed for this virtual machine

    Can't figure this one out and search Google is not come with much.

    I have 13 virtual machines in my environment.  They all use the same data store.  11 of them have no problems, but 2 of them fail with this error when you try to make a snapshot.

    I tried to reboot the hypervisor and vmware vsphere services.  I tried to remove and add the virtual machines of the inventory.  None of the VMs directories have snapshot of the files already.

    This usually means that you have material non-quiescable, as a tape device connected, or you have a persistence of defined virtual disk.  I recomment you latter by default and try again, because this is the typical cause.  Otherwise, other suspects are raw disk mappings (a fibre channel LUN) sent directly to your virtual machine, which cannot be suspended or IO DirectPath devices (USB or PCI cards series you will cross TSE of the VM).  If this is the case, you're probably SOL.

    I strongly suspect that you're a mode not supported on the persistence on a virtual disk to your virtual machine.

  • Transitions between States

    Struggling to learn FB4 transitions. The below simplified example code.

    Text boxes are intended to disappear and to move out of the screen must be replaced by the new text box that fades and moves on the screen.

    Screen 1 or 2 is ok, but after completing the transition from screen2 screen1 the textbox1 disappears.

    I guess it's related to the AddAction/RemoveAction placement but I tried all the combinations without success.

    Could someone tell where I have gone wrong.

    Thank you

    MB

    <? XML version = "1.0" encoding = "utf-8"? >
    " < = xmlns:fx s:Application ' http://ns.Adobe.com/MXML/2009 "
    xmlns:s = "library://ns.adobe.com/flex/spark".
    xmlns:MX = "library://ns.adobe.com/flex/mx" minWidth = "955" = "600" minHeight >
    < fx:Declarations >
    <! - Place non-visual elements (e.g., services, items of value) here - >

    < / fx:Declarations >
    < s: states >
    < name s: State = "screen1" / >
    < name s: State = "screen2" / >
    < / s: states >
    < s:transitions >
    < s:Transition fromState = toState "screen1" = "screen2" >
    < duration s:Sequence = target "1000" = "{[screen1_text, screen2_text]}" >
    < s:Parallel target = "{screen1_text}" >
    < s: bland alphaFrom = alphaTo "1.0" = "0,0" / >
    < s:Move xFrom = "200" xTo =-"500" / >
    < / s:Parallel >
    < s:RemoveAction target = "{screen1_text}" / >
    < s:AddAction target = "{screen2_text}" / >
    < s:Parallel target = "{screen2_text}" >
    < s: bland alphaFrom = "0,0" alphaTo = "1.0" / >
    < s:Move xFrom = "-500" xTo = "200" / >
    < / s:Parallel >
    < / s:Sequence >
    < / s:Transition >
    < s:Transition fromState = toState 'screen2' = "screen1" >
    < duration s:Sequence = target "1000" = "{[screen1_text, screen2_text]}" >
    < s:Parallel target = "{screen2_text}" >
    < s: bland alphaFrom = alphaTo "1.0" = "0,0" / >
    < s:Move xFrom = "200" xTo =-"500" / >
    < / s:Parallel >
    < s:RemoveAction target = "{screen2_text}" / >
    < s:AddAction target = "{screen1_text}" / >
    < s:Parallel target = "{screen1_text}" >
    < s: bland alphaFrom = "0,0" alphaTo = "1.0" / >
    < s:Move xFrom = "-500" xTo = "200" / >
    < / s:Parallel >
    < / s:Sequence >
    < / s:Transition >
    < / s:transitions >

    " < = xmlns:fx s:Panel ' http://ns.Adobe.com/MXML/2009 "
    xmlns:s = "library://ns.adobe.com/flex/spark".
    xmlns:MX = "library://ns.adobe.com/flex/mx".
    Width = "100%" height = "100%" cornerRadius = "5".
    backgroundColor = "#B6B8E8."
    title = "Transition between States example.
    includeIn = "screen1, screen2" >

    < s:layout >
    < s:BasicLayout / >
    < / s:layout >

    < s:BorderContainer id = "screen1_text" includeIn = "screen1" width = "400" height = "220" x = "200" y = "10" >
    < s:layout >
    < s:BasicLayout / >
    < / s:layout >
    < s:TextArea width = '95 percent' height = '95% ' >
    < s:textFlow >
    < s:TextFlow >
    < s >
    Text for screen 1
    < / s >
    < / s:TextFlow >
    < / s:textFlow >
    < / s:TextArea >
    < / s:BorderContainer >
    < s:BorderContainer id = "screen2_text" includeIn = "screen2" width = "400" height = "300" x = "200" y = "10" >
    < s:layout >
    < s:BasicLayout / >
    < / s:layout >
    < s:TextArea width = '95 percent' height = '95% ' >
    < s:textFlow >
    < s:TextFlow >
    < s >
    Text for screen 2
    < / s >
    < / s:TextFlow >
    < / s:textFlow >
    < / s:TextArea >
    < / s:BorderContainer >
    < s:Button includeIn = "screen1, screen2" x = "200" = "382" label = click on "Screen 1" = "{currentState ="screen1"}" / >
    < s:Button includeIn = "screen1, screen2" x = "530" y = "382" label = click on "Screen 2" = "{currentState ="screen2"}" / >
    < / s:Panel >
    < / s:Application >

    I try with a current version and this bug seems to be fixed. You can try to download the latest version of http://opensource.adobe.com/wiki/display/flexsdk/Download+Flex+Hero.

    -Kevin

  • Effect of movement not executed on the transition from State

    I have the following problem using view States, of transitions and the effect of movement

    I have a component panel and States state1 and state2.

    Panel is included in state1 but not in state2.

    When view state is changed from state1 to state2 I want to animate the front panel is removed.

    However, if I put a motion effect in my state of transition that it never runs because the Panel is removed before the effect plays.

    The only solution I found was to add a fade transition effect. This prevents the Panel to detach and the effect of movement is plays correctly.

    What continues? Is there a documentation explaining this? This could be a bug?

    Here is a sample application to demonstrate the problem. Panel1 has the problem and workaround Panel2.

    <? XML version = "1.0" encoding = "utf-8"? >

    " < = xmlns:fx s:Application ' http://ns.Adobe.com/MXML/2009 "xmlns:s ="library://ns.adobe.com/flex/spark" "

    xmlns:MX = "library://ns.adobe.com/flex/halo" >

    < s: states >

    < name s: State = "state1" / >

    < name s: State = 'state2' / >

    < / s: states >

    < s:Group >

    < s:Panel id = "panel1" y = "0" y.state2 = "100" title = "Group 1" includeIn = "state1" / > "

    < s:Panel id = "panel2" x = "150" y = "0" y.state2 = "100" title = "Group 2" includeIn = "state1" / > "

    < s:Button left = "300" label = "toggleState" click = "currentState = currentState == 'state1'? 'state2':"state1"" / > "

    < / s:Group >

    < s:transitions >

    < s:Transition fromState = toState 'state1' = 'state2' >

    < s:Parallel >

    <!-strange! 1 Panel is removed before the effect of movement time->

    < s:Move target = yTo "{panel1}" = "100" / >

    <!-the workarount. With a mannequin fade effect panel2 stays visible and move effect is executed->

    < s:Move target = yTo "{panel2}" = "100" / >

    < s: bland target = alphaTo "{panel2}" = "1" / >

    < / s:Parallel >

    < / s:Transition >

    < / s:transitions >

    < / s:Application >

    What is happening here is the Panel is removed from the DisplayList at the beginning of the transition before the passage has a chance to occur.  This happens by default unless someone tells the transition to remove the item at another time.

    There is a special logic built into bland who knows when an element is removed from the DisplayList so that he knows to say the transition to weaken the element before removing it.  This is why the workaround you mentioned works for your case.

    You will notice that if you use:


    The target fades out as long as his movement before retiring from the DisplayList.

    Normally, in this situation the transition must know when to remove the item from the DisplayList and you can tell him that using the RemoveAction tag, for example:

    http://ns.Adobe.com/MXML/2009"xmlns:s ="library://ns.adobe.com/flex/spark">
       
           
           
       

       
       


           
       
       
       
       
       
           
               
                   
                   
               

           

       

    Note that in this transition, I use a sequence and put the RemoveAction after the move, so the transition knows to move the item before removing it.

    By the way, thanks for the great code example!  When posting code on here is compile concise, complete, and I can quickly copy and paste into Flash Builder, I'm much more likely to focus on the issue.

  • Calendar of transition control in several multi-state objects

    How can you control the timing of multiple transitions multistate DPS? If you have two slide shows with a single button by telling everyone to go to a particular State, the transitions go in sequence rather than simultaneously. You can adjust the schedule so that everyone goes at the same time and for the same duration?

    Currently, you cannot run two actions button at the same time.

  • Weird bugs when using transitions

    I am using a transition to a simple collapse/uncollapse of a component and I get weird questions. The main problem is that whenever the animation ends, it restores the coordinates he began to reason any and I can't figure out how to make it stop. Here is the code I use to animate. Just for reference, the current values of the _openY is - 73 and _closedY is - 13. So once the animation is completed each time he ends up back at-13 for some reason any.

    <s:states>
         <s:State name="closed"/>
         <s:State name="open"/>
    </s:states>
         
    <s:transitions>
              
         <!-- Transitions from the closed to open state, animating it shrinking and the icon rotating to point downwards -->
         <s:Transition fromState="*" toState="open">
              <s:Parallel duration="300">
                <s:Move yFrom="{_closedY}" yTo="{_openY}" target="{this}" />
              </s:Parallel>
         </s:Transition>
              
         <!-- Transitions from the open to closed state, animating it growing and the icon rotating to point upwards -->
         <s:Transition fromState="*" toState="closed">
              <s:Parallel duration="300">
                   <s:Move yFrom="{_openY}" yTo="{_closedY}" target="{this}"/>
              </s:Parallel>
         </s:Transition>
              
    </s:transitions>
    

    If someone an idea how to solve this problem? I hope there's something simple I'm missing here.

    You should not use side-making values such as yFrom/yTo in your transitions, but rather to define these positions in the State values and let the transitions understand them automatically.

    See http://forums.adobe.com/message/3130755#3130755 for an example

  • Make state transitions within a component of DataList

    I have a datalist that includes a word bubbles title, data and long list of text for each line in the list of data. I want this to appear as the title, date and a word bubble extracted text. When the user clicks on it, I want the text box expand to show more text. To do this, I went into the isolation of the repeated item mode. In the "Selected" State, I enlarged the text box and made a smooth transition. It works exactly as I want it. Now, I want to click a button box and the box shrink to the way it is 'normal '.  However, when I try to add an interaction to the button while in the 'selected' State the menu interactions I cannot choose a State play transition to and the ok button is grayed.  Once the user clicks on the text, he enlarged and is now frozen this way that I'm not able to add a way to transition to the 'normal' State

    The reason seems to be that if you are in a 'normal' State, you can easily select the 'selected' State However, there is no natural transition of the "selected" back to 'normal '.

    Hi infomotive,

    The logic that controls which list item is selected is determined by the selectedIndex from the list. When you click an item, selectedIndex of the list has the index value of that element, which puts the appropriate in repeated item in turn has "selected" State (and puts the previously selected item in its 'Normal' State). All this is done for you by Flex, and you cannot directly control the State of a repeated element (or, in fact, no matter which component skin!). In order to state of an item to 'Normal', you set selectedIndex from the list to not be the point.

    You can do this by creating an action sequence with effect of the value of property that affects the selectedIndex property of the list - 1 (which means that nothing is selected). Unfortunately, this is impossible within the repeated element itself because the interaction Panel won't let you target objects that are at the top of the hierarchy of the source of the event! So actually there is no right way to do what you want to do in the last version of Flash Catalyst. However, it is quite easy in Flash Builder:

    -Adam

  • Problems with the Transition of custom components bare in s:TileGroup

    I have a problem with transitions play does not correctly on a custom component that is displayed in a < s:TileGroup >.

    Code of the custom component;

    <?xml version="1.0" encoding="utf-8"?>
    <s:SkinnableComponent xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark"
     skinClass="com.mydomain.view.skins.SkinFile">
     
     <fx:Metadata>
      [SkinState("normal")]
      [SkinState("photo")]
     </fx:Metadata>
    
     <s:states>
      <s:State name="normal" enterState="invalidateSkinState()" />
      <s:State name="photo" enterState="invalidateSkinState()" />
     </s:states>
     
     <fx:Script>
      <![CDATA[
       override protected function getCurrentSkinState():String {
        return currentState;
       }
      ]]>
     </fx:Script> 
     
    </s:SkinnableComponent>
    

    The skinfile itself is relatively simple

    <?xml version="1.0" encoding="utf-8"?>
    <s:Skin xmlns:fx="http://ns.adobe.com/mxml/2009" 
      xmlns:s="library://ns.adobe.com/flex/spark" 
      xmlns:mx="library://ns.adobe.com/flex/mx"
      width="300" height="200" width.photo="140"
      >
       
     <fx:Metadata>
      [HostComponent("com.mydomain.view.components.MyComponent")]
     </fx:Metadata>
     <s:states>
      <s:State name="normal"/>
      <s:State name="photo"/>
     </s:states>
     
     <s:transitions>
      <s:Transition autoReverse="true">
       <s:Resize target="{this}" duration="500" />
      </s:Transition>
     </s:transitions>
     
     
     <s:Rect id="rect" radiusX="15" radiusY="15" top="0" right="0" bottom="0" left="0">
      <s:fill>
       <s:LinearGradient rotation="90">
        <s:GradientEntry color="0xffffff" ratio="0" />
        <s:GradientEntry color="0xf0f0f0" ratio="1" />
       </s:LinearGradient>
      </s:fill>
      <s:stroke>
       <s:SolidColorStroke color="0xc0c0c0" weight="1"/>
      </s:stroke>
     </s:Rect>
     
    </s:Skin>
    

    When displaying a couple class MyComponent instantiated in a s:TileGroup as follows;

    <s:TileGroup width="940" verticalGap="20" horizontalGap="20" clipAndEnableScrolling="true">
     <components:MyComponent currentState="{theState}" />
     <components:MyComponent currentState="{theState}" />
     <components:MyComponent currentState="{theState}" />
     <components:MyComponent currentState="{theState}" />
     <components:MyComponent currentState="{theState}" />
     <components:MyComponent currentState="{theState}" />
     <components:MyComponent currentState="{theState}" />
     <components:MyComponent currentState="{theState}" />
     <components:MyComponent currentState="{theState}" />
     <components:MyComponent currentState="{theState}" />
     <components:MyComponent currentState="{theState}" />
     <components:MyComponent currentState="{theState}" />
    </s:TileGroup>
    

    and saw two buttons to switch the value of the 'State' to 'Normal' or 'photo', it resizes the component properly to the small size, but that goes back to the smaller size to the largest size, it does not play the transition. It just makes small to large immediately.

    The strange thing is, however, that if I use a tag < s:HGroup > instead of < s:TileGroup > it works like a charm, so I guess that's not so much the custom component or skin that is causing problems.

    When I put the transition of the size of the component itself instead of in her skin, then it works as expected, but I think that transitions should be defined in the skin and not in the component itself, right?

    I do something wrong or didn't I just encountered a bug maybe?

    It took me a while to realize it was.  TileLayout organises its elements in a grid of 'cells' and each cell is the same size (the size of the largest component).  Then, each element is placed in its own cell because the horizontalAlign/verticalAlign properties.  By default, TileLayout a horizontalAlign = justify which means that extends the element to the size of the cell.  In order to have an effect of resizing plays on the skin of the element does not really have any effect.  He gets to work when the shrinkage, but fails more and larger, I guess because the increase in the width of an element affects all cells, while the lower has not.

    So I think the right thing to do here is to either wrap a group around the Rect and mentioned target that you like, or the TileGroup.horizontalAlign left/center/right value.

    Here's a simplified example of how you can reproduce it:


    http://ns.Adobe.com/MXML/2009.
    xmlns:s = "library://ns.adobe.com/flex/spark" >
       
            [Bindable] public var test: Boolean = true;
    ]]>
       

       
       
           
               
                   
                       
                       
                       
                       
                   

                   
                   
                       
                           
                       

                       
                           
                       


                   
                   
                   
                       
                   

               
           
       
       
       
           
       
       
       
           
       

       
       
           
           
       

       
       
           
           
       

       
       
           
           
       

       

    If you wish, you can ask about a bug, but I have the feeling that we would not be can not fix because probably you shouldn't use horizontalAlign = justify and change the width of the element at the same time.

  • State Machine with PID control

    Hi, I currently have a problem with my state machine, I control two cylinders double effect in sequence that works very well. However, there is one point I need to increase the pressure in the cylinder and to maintain this pressure through the sequence of State machine, however when the state machine transitions to the next indicate the PID controller resets, how can I solve this problem? Everything in is also allowed to apply the pressure in the cylinder another (same node IO accessed).

    Thank you I joined my project in a WinZip file, then it will have to be extracted. The two main VI to watch is 'Park Brake FPGA VI New' and 'park brake host VI update 2 "(new)

    Thank you.

    Nevermind I solved the problem with a parallel loop.

  • where to submit bugs / improvements

    Hello

    I wonder if there is a place dedicated to minor or major improvements or supposed bug... In the past, I did it in this forum, but it might be a bit boring for others? Also, I expect a response to OR if reports of some unexpected behavior, etc., while in the forum not all entries can be filled.

    In addition, it might be useful if there is a site featuring all the officially recognized problems - it would help if you meet a 'strange' and this behavior already listed there - or not.

    Recently, I learned from this link (and not hidden) where to submit feature requests, and I thought of something similar... It does not exist, or it would be possible to implement?

    Of course, I can send annoying comments here, too, such as: in the target generation/settings/Version Info the checkmark label should read "Preview Substitutions' instead of"Substitutions Prevew":-)

    Wolfgang

    Fake Hello,

    You can always ask here about the State of any bug or suggestion. I don't know if we always do, but we do not usually post the bug report ID so that you can ask about it later. But even if you do not have the bug report, you can just a link to the original discussion forum and we should be able to track it down.

    Regarding the general question to all available outside current known issues, it is a request that we have heard and we hope to eventually get there, but it is not a trivial thing. Our current bug report database has a large number of items that refer to internal issues only (i.e. problems found internally on the versions not released CVI) and also contains the questions duplicate, trivial problems, non-bugs (tasks), false alerts, reports of bugs that have not yet been considered, etc., etc. It is not a trivial task to filter the "known issues" that are relevant to our users, as well as determine exactly all versions of the product that have the bug. For example, create a list of corrections that you see when a new version of the CVI is available is always an intensive process of enough work, but it's doable because tracking of fixed bugs is very different, followed by outstanding issues.

    That said, we have not given up the idea, and we hope to eventually do something like this, because we are aware of the usefulness, it's customers.

    Luis

    NEITHER

  • Transitions in VBAI

    Hello

    We use VBAI 2010 and a smart camera for a vision project. In VBAI we have programmed a programm with some States that are connected by transitions. Now, we have a question:

    If there are several state transitions which are true which will be taken? Are there rules concerning transitions in which line, that they be verified?

    Greetings

    Oliver

    No, this feature has been around since we introduced the State-transition diagram. Right-click on the STATE, where transitions begin (not on the transition).

    This option is available only when there are more than 2 transitions that come out a State (not counting the default transition).

    Christophe

  • Research of software bug

    Hi team,

    Cisco removed the ability to search for known bugs in a particular software version?

    The new tool of bug seems to allow seraches if you know the ID of the bug.

    All my attempts to locate the old dialog box where you enter platform and software information ended up in this new tool.

    The link of display bugs in advising software also now just takes you to the new bug tool.

    How am I supposed to identify a potential bug that we are witnessing on our infrastructure when I clearly do not know the ID of the bug?

    The information on the link for this tool States 'Finding software bugs based on the product, release and key word'. I don't see how this is possible.

    Thank you.

    Hello

    I see that you do not have an assosiated to your Cisco.com user ID valid service contract. To search for bugs in products or releases, you need a valid service contract in your Cisco.com user ID.

    If you do not have a service contract you can get one through:

    • Your team if you have a purchase contract direct with Cisco Cisco
    • Your Cisco partner or reseller

    Once you have the service contract, you must associate your service agreement with your Cisco.com user ID with the Profile Manager

    https://Tools.Cisco.com/RPFA/profile/edit_entitlement.do?tab=3

    Thank you

    Kavita

  • Status of transition-NOT AUTHORIZED

    Hi all

    We have configured successfully Dataguard environment and we also tried the swichover scenario.

    but when downshift us switch on the status of the new primary database is NOT AUTHORIZED.

    In the new primary database, the State of the database role years crossing is as follows

    primary_ord.png

    In the new base standby state of transition from years of database role is the following

    primary.png

    can anyone help on this.

    Hi Royce

    This means that a request for digital switchover has not received from the primary database. If this isn't a problem. While you make the transition to digital, you will see that the status is "in the primary.

    https://docs.Oracle.com/CD/E18283_01/server.112/e17110/dynviews_1096.htm

    Yasin

Maybe you are looking for