Was reading the blog post; http://www.spotify.com/uk/blog/archives/2012/02/23/spotify-now-with-gapless-playback-crossfade/
Downloaded the preview and now font face is disabled. We've tried eot, woff, ttf, svg. In the network panel, only SVG loads in, but in the preview tab and on page it renders as Times New Roman. It was working before, but now doesn't work with our current implementation or a stock font-squirrel implementation. Any ideas, it worked fine in 0.8.10.3
EDIT - SVG works, but not .woff or .ttf as before. All of them work in 0.8.10.3
This has been temporarily disabled in the new version due to memory leaks and unexpected crashes of the client.
We'll enable it again when we upgrade to a newer version of Chromium Embedded Framework.
That's not all that doesn't work. Now, gapless playback, crossfade and even the repeat function are stuck on (the last intermittently as my playlist sometimes repeats and sometimes does not, though the repeat annunciator remains off). The boxes for gapless and crossfade are unchecked. If I check them, close the client, start it again, uncheck them, close the client and start it again, the boxes remain unchecked, but the ferstunkener build 572 still messes-up the transitions, truncating up to five seconds or so from the start of each cut.
Related
I'm developing a locked down tablet app for students meant to bring up a testing website. Currently the site uses the asp.net version of the CKEditor control with no problems in Safari.
However, when I try to use the editor with the UIWebView control (because of the iOS versions we are committed to supporting, I cannot try other controls like WKWebView) I run into two issues:
The cursor seems to run away from the text (from what I can tell this spacing seems to have to do with spaces specifically although given how slowly it moves away from where new text is entered, it's hard to tell).
When the cursor reaches the bottom of the text box it will simply move below it, rather than adding scrollbars.
Is this simply a matter of the lag between the development of the base CKEditor control and its conversion to ASP.NET or is this a fundamentally broken part of the control?
For some reason i am not able to enter any text in inputtext in dhtml environment. The same is working fine in swf10 environment.
When i hover over the input text i observed that the cursor is not changing to selector. It looks as if the onmouseover event of inputtext is not getting fired.
Has anyone come across this kind of issue in openlaszlo dhtml envrironment?
I am using OpenLaszlo 4.9, Windows 7 and the browser is Firefox 15.0
I found a bug report in jira http://jira.openlaszlo.org/jira/browse/LPP-9934.
Please suggest any ideas to overcome this issue/
The problem you are seeing is probably connected to the way OpenLaszlo replicates the behavior of clicking through Sprites or visual elements in the Flash runtime for the DHTML/JavaScript runtime. Until recently browsers didn't support that kind of functionality directly. Therefore the OpenLaszlo team had to use a workaround, which is described in detail in this comment on LPP-5447.
Clickdivs exist to have independent control over clickable sprites,
without interference from regular divs. They are placed in a separate
copy of the regular lzdiv sprite hierarchy so we have more control.
This also provides a place to put focused inputtext divs so they are
in the foreground and clicking/dragging to edit works properly.
The clickdiv functionality seems to be broken from time to time with browser updates or due to regressions. In 2012 some improvements to the DHTML runtime click-through functionality were done, using newer browser features in Firefox (which now allows to click through div elements using the CSS style pointer-events). Since the clickdiv functionality is part of the LFC, fixing that functionality in your application is not advised.
You can test if the inputtext works by tabbing through the components until your inputtext element has the focus and start typing. If the text can be entered as expected, but you cannot click the component with your mouse to select it, it's definitely a clickdiv problem.
Update: Tested with OpenLaszlo 4.9.0 and various browsers
I've tested with OpenLaszlo 4.9.0, DHTML runtime and IE9, Firefox as well as Chrome, using the test case attached to LPP-9934: All browsers show that specific bug behavior. If the bug has not been filed, please file a JIRA bug.
i don't work on Flash much but i've made a small banner ad for a client...
its a simple banner with 3 images in it and a button with some actionscript linking to an external campaign monitor.
the target file size is about 70kb.
image compression is turned on in the publish settings.
without the button the file size is fine.
when i add a basic button in with a an event listener and about 5 lines of code the published swf size jumps up to over 200kb...
i've tried deleting the button and it drops back to 70kb...
anyone know what i can do to include a button but also keep the file size reasonably small?
cheers
dog
Are you using text in your button and have you embedded the font? That can really bloat an swf.
What you can try is either break the text apart so you don't need to embed the font (but it makes editing a lot of work)
Or you embed only the characters you have actually typed in the button.
If that is not the problem, please post any more details you can think of, including the code.
Check if you have any images in Flash Library that has Linkage id assigned to it. Remove the linkage id and publish swf.
well, it looks like it was a bug in CS5... i tried opening the banner in flash CS6 and did the same procedure of creating the button and giving it an action... published it and it was now approx 40kb...
very odd.
I've been experiencing some very strange behavours in an app I'm developing. The app is not very advanced, it stores a couple of places in a sqlite database and is displayed in listviews, on a mapview etc. So, when browsing through my app after deploying it to my phone everything works great, but after a while one listview doesn't get inflated. A scrollbar appears as if the items were there but I can't see them. I push the back button to close the app. When revisiting the app my first view, which has two buttons, gets all messed up. The buttons fill the viewport and the background disappears etc. I can't figure out what's wrong.
Anyone else facing these problems? My phone is a HTC Desire HD with Android 2.3.5
The app is pretty "layout heavy", if you know what I mean. The listview items has custom background images, I'm using custom fonts etc. But the app is running smoothly up to the point when it freaks out and displays/don't display everything wrong.
My first thought is there is some kind of memory issue, ideas?
EDIT:
I believe this might have something to do with defining and using #00000000 as transparent color. Use #android:color/transparent instead.
SOLUTION:
So after doing some testing I found that what I previously mentioned in the edit really is the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
After some testing I finally found the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
So to fix this problem you should use #android:color/transparent instead when you want transparency on, for example, a view background.
If there are memory errors you should be able to catch them in logcat. You'll get "VM failed on xxxx byte allocation" messages (or the like).
Silly/stupid answer: often when I run into layout issues within my app, it's because I needed to do a clean build after having changed my layouts. You might want to start there.
Edit: You might also try the emulator, and if you suspect memory issues you could start the emulator with a small heap to force the issue to occur sooner. You can also check your heap usage in DDMS or with the Eclipse MAT to see if it's leaking.
I was experiencing the same problem on Galaxy tab even with #android:color/transparent. Was able to fix it only by replacing android:background="#color/transparent" with android:background="#null".
We have this Flex app built on Builder 3 and we're using SuperTabNavigator from FlexLib to have some modules displayed. The thing is, whenever the user resizes the browser window all the contents on any tabs open simply disappear and there's no way to get them back. This only happens the first time, so if you close these 'broken' tabs and reopen them, you can resize all you want, but you still lost all you were doing in them and this is unacceptable. I've done some testing and found the module in that tab doesn't dispatch the resize events when this happens. It's dispatched when it opens (everything is set to 100% to fit the browser window, so it resizes on startup) and every other time you resize it without 'breaking' it. It gets weirder. I've also found that resizing works perfectly as long as you resize it to a size larger than the original (i.e. you open it in a browser window that is restored and then maximized), but even after doing that, if you change its size back to something even a pixel smaller than the original, the module just disappears. Everything else remains in perfect working conditions: any components outside tabs and the tabs itself work, but (summing up) anything within any tab open at the moment you first resize the browser window to a size smaller than the original just disappears.
I understand that this is a weird problem and hope some of you might be able to help me. Feel free to ask any questions if anything wasn't clear.
Thanks in advance.
I had this exact same problem with my application. The issue stemmed from the fact that the RemovedFromStage event was being fired when the window was sized smaller than its original size. I was catching the RemovedFromStage event and hiding my component, which resulted in this behavior. A more detailed explanation can be found here.