Hi, I know this issue was told before but there was never an answer. If you click on an rss-item (in the list of rss-items) you go to the url (link). If you go back to the rss-list you'll see that the row you just selected is highlighted. When you scroll the highlighted item out of the screen and pull it back to view it, all text and image are gone!!! Only way to retrieve the text and image is to reload the list. Is there a way to solve this??? Best Regards, Danny

Not really a proven method to solve this. The issue is with the way the UITableViewCell is being recycled / or not. There are tons of ways that the menu lists could be configured and only some of the ways seem to cause this problem. I think more than anything the Custom UITableViewCell we created is trying to do "too much" to satisfy all the different possible options in the control panel. It seems like maybe a few different menu plugins should be created, one for each different type of setup. Example: With images. Without images. With images 57x57, with images 72x72, etc. If this were done then the custom UITableViewCell wouldn't not have to "understand" as much and would render more efficiently. The file in question is BT_cell_menuList.m in the Objects folder. This cell is used for all the different scenarios. If you want to experiment, you could do one of two things. You could a) Use a standard UITableViewCell instead of the custom one. This would produce a much more efficient cell but would not necessarily support all the control panel options. You could b) Create a simpler, less sophisticated UITableViewCell that understood exactly how to layout itself so it didn't have to process all the options in the control panel. If you look at BT_screen_menuList.m, you'll see where the custom cell is used in the cellForRowAtIndexPath method. This method's purpose is to return the cell for each row. Changing: BT_cell_menuList *cell = (BT_cell_menuList *)[tableView requeueReusableCellWithIdentifier:CellIdentifier]; to UITableViewCell *cell = (UITableViewCell *)[tableView requeueReusableCellWithIdentifier:CellIdentifier]; Would tell the menu list to use the standard cell. You could also set it to use your own. Not sure how this will get resolved long term. I like the idea of simplifying the options for the menus and making more plugins to accomodate for each type of menu. Less breakable is an important concept.

Hi David, Thanks for your answer(S). I get your point but I see apps with a lot of different items in one cell (and I guess you can read here:options). How are they doing this? Saw your app Telediario and the rss doesn't seem to have the described problem. What did you do different? Ofcourse you can create more different menu plugins but I think (and that's the way I try to accompish) it would be best to give every screen (if it uses tableviewrows) it's own custom menu list (if the screen needs it). In this way the user of the plugin has always the right menu list and doesn't have to install a certain menu to have the (full) functionality of that screen. Regarding the quantity of options: less options = less breakable I agree. But to have your app looking better than ever it's important to have many options. Users of apps (and Apple) like good looking apps and prefer them above bad looking apps. (can't find the article anymore but read something about a big survey they did) There has to be a way to have many options in a non-breakable way. But what's the solution. I really like to hear if you ever find a way to accomplish this. Best Regards, Danny

Interesting. I just noticed this last night when i was testing my RSS/Twitter feed. I saw the 2 blank cells when i was returnignt o the page from reading a tweet. i thought it was just a screen refresh or maybe a device bug on my old iphone 3. I'm still playing with this plug in as i just implemeted it yesterday, thought it could be my config too. I was hopeful at worst it was a simple caching issue or maybe even a font color problem. like since i visited the 'link' the A:visited tag may have been re-styled inthe code and was just a font color that i couldn't see. (my screen is a black backgound here) can't say i'm glad to hear it's a little more than that, but then again i think Danny would have figured out a font color issue. LOL. i'm kinda scared that i'm starting to understand david's posts better these days....not enough to fix it but 3 months ago that stuff made ZERO sense.