A quick tip for all not seeing their embeded fonts when compiling pure AS project with Flex SDK 4:

[Embed(source=“assets/fonts/my-cool-font.otf”, fontFamily=“CoolFont”, fontWeight=“normal”, mimeType=‘application/x-font’, embedAsCFF=‘false’)]

Notice the embedAsCFF=‘false’, this is the most important part. Basically when not using Spark Text Components (which are based on Text Layout Framework) you need this option.

In summary Halo Components or pure Actionscript Projects (TextField) need embedAsCFF=’false’ when embeding fonts in Flex4.

To fix the recent bug with VMware Player 2.5.3 and Workstation 6.5.3 Build 185404 under Karmic Koala Ubuntu just paste this line in your console before launching vmplayer/vmware:

export VMWARE_USE_SHIPPED_GTK=yes

you may also modify the VMware starting script so you don’t have to export it every time.

If you get this error on each frame then you have probably moved the camera to the same position as the object (camera.z = 0). Change it a bit and the error should be fixed.

First of all let me apologize for not blogging in a while but I’ve been working on couple of interesting projects after which it was time for deserved vacation on the BlackSea’s beaches.

Anyway I needed a better looking horizontal slider for one of the projects and all of my googling got me nothing reasonable (most of the tutorials were for changing the Thumb and leaving the default TrackHighlight) so I had to figure out something. Here is my horizontal slider, it is pretty basic but you can use it as a base for your needs. Corner Radius and Background Gradients are set via CSS, width and height are flexible too. Check the example and get the source code

With no surprise the update from Interpid Ibex to** Jaunty Jackalope** was not as easy as I hoped. After booting the fresh 2.6.28 kernel I was welcomed with “Press enter for maintenance (or type Control-D to continue)” and errors when trying to mount my RAID0. After some investigations found that the devices are now named md_d* and there are some devices in /dev/md/.  Because of this change I had to do the following things to get my raid up and running:

1. Reassemble the raid (check if it is inactive with less /proc/mdstat) – in my case the command looked like this: mdadm --assemble /dev/md_d1 /dev/sdb2 /dev/sda5
2. mdadm --detail --scan >> /etc/mdadm/mdadm.conf and comment your previous ARRAY definition in the config file
3. Modify /etc/fstab if needed

Also if DKMS fails to build the new NVIDIA driver be sure to check that you have installed the headers files (the upgrade process did not install them for me).

Again : I’m NOT responsible for any damage or data loss you might experience. Backup often, backup soon!