Search Results

Search found 3 results on 1 pages for 'luuk'.

Page 1/1 | 1 

  • Chrome messes up the website layout, FF and IE is good

    - by Luuk
    I am working on a website: http://www.bbp.nl/luuk-test/wac It displays really well on FF and IE. I went tot test it in chrome and it is totally messed up. Somehow chrome displays all the divs underneath each other. I really dont know where to look since it also validates well in W3C validator. Also googled it, but could not find anything. Does anyone knows the answer? Please help.

    Read the article

  • Weird bug in header in IE7

    - by Luuk
    Hi all, I have a weird bug in IE7. http://www.luukratief-design.nl/dump/simplefolio/ the navigation has to be centered. same goes for the background. Now every browser does it perfectly. even IE6! (didnt do pngfix yet). The only one who is having problems is IE7 who shifts the whole navbar element to the right. Anyone knows how this is possible?

    Read the article

  • Retaining Managed objects - more general retaining objects

    - by Luuk D. Jansen
    A quick question regarding Managed Objects. I created an Array with Managed Objects (in Object 1: TableViewConbtroller), and pass one of those objects to another class/object (object 2: TableCell). The original array should still be retained in the original caller class. Then Object 2 is released, does that mean that that particular item in the array is released as well, as the reference to it in Object 2 was released? I am trying to better understand how to work with ManagedObjects as I get 'Object was released' errors. [EDIT] After some experimenting I came across the following scenario: I have the main AppDelegate. In a different class I create an AppDelegate to obtain the ManagedObjectContext. appDelegate = (iDomsAppDelegate *)[[UIApplication sharedApplication] delegate]; [self setContext:[appDelegate managedObjectContext]]; When the class is finished, and I release it, the variable in the class 'appDelegate' is also released. But then the ManagedObjectContext is closed, and obvious any future attempt to use it will cause a crash. So should I leave the appDelegate unreleased? This comes to the same question as the above about when and how to release in those situations where an objects is used from another class. I think a way of putting it is, how to know when you own an object and when not.

    Read the article

1