Community
Participate
Working Groups
uncaught exception: Animation aborted: AnimationRenderer failed: TypeError: $1 is null construct(Object { name="$0"}, Object { name="$1"}, Object { name="$2"})teleko...6238539 (119. sor) construct(Object { name="$0"})teleko...6238539 (119. sor) construct(Object { name="$0"})teleko...6238539 (120. sor) construct(Object { name="$0"})teleko...6238539 (120. sor) construct()teleko...6238539 (120. sor) [Break on this error] qx.Class.define($[1560],{extend:qx.cor...[$7][1],$2[$7][1])];}return $5;}}}}); /Details:/ The error is not general, and it happens only in RAP 1.4, not in 1.3. - We have a Dialog, which has a Canvas, and some Button-s and Label-s on it with some static images set as the background of some widgets. It is also managing an UI thread, to supply the UI updates of the Canvas (it's eventually a player, so a play button starts a UI thread, which is iterating over our frames until stopped) - The whole dialog is a mess under RAP 1.4, and I'm quite sure the problem is under the hood. I couldn't isolate the problematic part in RAP code, so I write down the symptoms and hope you find out something from it: % We have a Button bar with 6 buttons in a GridLayout. When there is any :hover style on it, then on mouse over, the :hover style is applied, but on hover-out it doesn't change back. In Firebug, I can see the above error. % We have two 12x12px buttons for stop and play. I set two different images as the background of play and stop, but on the UI both of them will have the image set for play, no matter what I do. Also, because they are buttons also, when hovering out, the stuck in their :hover style % These symptoms occur also if I move my stop and play buttons to another view. I'm sorry, but that's all I could figure out from the behaviour, I'm available if you need info. Regards, T.Cs.
It seems that this is the place where the exception occures: setRenderFunction:function($0,$1){ if(this._renderType==null){ this._renderFunction=$0;this._context=$1; } } Hope it helps.
I rerun the case in Debug mode, and it was a little more verbose. I found a _render() function in 68119 _render : function( transitionValue ) { 68120 if( this._active ) { 68121 var convertValue = this._cloneFrom != null 68122 ? this._cloneFrom.getLastValue() 68123 : transitionValue; 68124 try { 68125 var value = this._converterFunction( convertValue, 68126 this._startValue, 68127 this._endValue ); 68128 this.renderValue( value ); 68129 } catch( e ) { 68130 throw "AnimationRenderer failed: " + e; 68131 } 68132 } 68133 }, 68133 }, At this position, this._startValue is null, which causes exception in the _converterFunction call. Sorry for the useless previous reports. This seems to be something to start at. Regards, T.Cs.
Can you provide a java-snippet or bundle to reproduce the problem? This could help us finding and fixing the bug MUCH faster.
I'd have to send you the whole class implementation, which I am not allowed to do currently. I'm really sorry. As far as I can tell, the getValueFromWidget function tries to get old background color before animating, through _style, but the property is not defined, so it remains empty string, which becomes null. I hope this helps.
Hmmm... there is a check to prevent this sort of thing, and it works fine when i try it. Unless you provide more information or a snippet, i really can't do much. Lets try to get some useful info: 1. What theme do you use? If you use your own, how does the css for the button in question look like? 2. Do you set a background, font or image on the button using java? 3. Does it still happens if there is no UI-Thread, no Canvas, or both?
> 1. What theme do you use? If you use your own, how does the css for the button in question look like? We use custom theme, tried it with removing every CSS, and problem still occures. The CSS we use: Button.animctrl-button{ border: none; background-color: #ffffff; } Button.animctrl-button:hover{ background-color: #323232 //Some other color } Button.animctrl-button:selected{ background-color: #121212 //Some more other color } So this way through the transparent PNG the color of the stop and play shapes change on hover. However, the problem is introduced with 1.4, and if I set animation: none; The problem is gone, so it's related with that, but I experienced it at other places where animation is not set to none. > 2. Do you set a background, font or image on the button using java? Yes, I set the Images I mentioned with setImage() from Java. None of the others. We experience another problem here, turned out to be independent from the other: - I create an Image with Activator, then create another one right after, and after that, both Image objects, altough on different address, contains the same image. The symptom was that the lastly created image is shown on both buttons. Doesn't happens with setBackgroundImage(), but that way I don't have transparent background. But this problem doesn't go away with animation: none, so I thinked it is (on first level) unrelated. Maybe another bug, for this one I can provide a snippet: play = imageManager.getImage("img/telekom/telemetry/play.png"); stop = imageManager.getImage("img/telekom/telemetry/animctr_stop.png"); imageManager is an instance of a class, that uses Activator and a cache to get the image. Each image is allocated only once. It binds to a view or shell, so when the master is disposed, it is getting disposed with each image allocated. THe same problem occures if play = Activator.getImageDescriptor("img/telekom/telemetry/play.png").createImage(); stop = Activator.getImageDescriptor("img/telekom/telemetry/animctr_stop.png").createImage(); > 3. Does it still happens if there is no UI-Thread, no Canvas, or both? Yes, I suspected that it is involved with the UI-Thread, but the problem also doesn't go away if I disable UI-thread, Canvas, or Both (tried all of them, but I will double check it).
Okay, i finally managed to reproduce it. All i had to do was to change the gradients in the default button-theme to solid colors and test it in the controls-demo. Strangely, in the examples-demo the exact same scenario exists ("Theming"-page) and works fine...
D***it, I forgot to mention that we use solid background. Happy you got it.
Okay, i guess this is a duplicate of Bug 313216. *** This bug has been marked as a duplicate of bug 313216 ***
Okay, 313216 is fixed. Please check if your issues are gone, otherweise reopen or open an new bug.
