It doesn't mean the team can't change its decisions, right? You'll experience lots of problems with the itembased approach. The model-view architecture handles some aspects of the application on its own. Without it, you'll have much more coding to do.Originally Posted by ankurjain
And the problem is...? Drawing the selection is the views and delegates responsibility. You have a selection model associated with the view and you can act depending on its contents.I actually want the border around the cell( sry for bad english ) or if a row is selected the border ( rectangle ) around the row.
I don't quite understand... You want to have two different kinds of editors? That surely doesn't require changing the delegate upon a click on the cell.i am calling the editor in the delegate. as one requirement was like that, bigger editor window on dbl clking the cell.
Of course you can.Can i edit data also and update it in Model/View architecuture ??
It's not that much more work as you think. And you'll probably save some time later. It's better to correct misdesigns earlier, because the consequences of such misdesigned won't require as many changes to the application as when you want to correct them on a later stage.Also deadline is close for 1st release, so i can't change the design right now.
Bookmarks