Re: D2006 Object inspector component
- From: "Maarten Wiltink" <maarten@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 26 Mar 2008 14:44:17 +0100
"DoctorC" <ecolautti@xxxxxxxxxxxxxx> wrote in message
news:47ea4f61$0$31421$f69f905@xxxxxxxxxxxxxxxxxx
Maarten Wiltink pisze:
"DoctorC" <ecolautti@xxxxxxxxxxxxxx> wrote in message
news:47ea20e9$0$31423$f69f905@xxxxxxxxxxxxxxxxxx
[...]So what do you suggest? Which component.
I meant between a drawgrid and a virtualtreeview :)
Oh, okay. I didn't get that. (-:
To tell the truth, I'd probably use neither. I'm a treeview kind of guy.
By all means don't let that stop you. You made it clear that it's not
what you want, and people have in the past made it quite clear to me
that they didn't like my choices all that much, either. Which never
stopped me.
Thanks for your help. It really helps to check with someone else.
I chose the two lists because they are really simple. I was worried too
about the consistency between the lists but it is quite simple to manage.
Just manage, or enforce? (Could you mess it up from outside the object?)
I'm going the way you described (object insted of records) for the
second part of the program, as I wrote before.
Indeed I have some experience with Delphi. The problem just baffled me.
Displaying such a kind of unusual data...
Not that unusual, I'd say. Basically, it sounds like dsplaying a standard
recordset in a grid or matrix. Having the records divided into categories
adds a little complexity, but nothing unmanageable. It does make life
harder on the display component.
The most important thing is to keep object layout and screen layout well
separated. On the other hand, a screen layout that matches the object
layout more closely makes for easier programming, not in the least when
you want to allow editing. The lesson in that is that a good design (of
the object layout) pays off.
Infact I don't know if it's worth creating a structure for such few
records or i.e use the virtualtreeview structure to hold the records.
That's because I still don't know what to use to display the data. Maybe
a "2-tier" solution is more universal even if it may be a waste of
resources in this case...
With so much resources to waste, use some of them to your advantage.
If the code becomes 200% slower and 100% more readable, do it.
What do you mean by '2-tier'?
Groetjes,
Maarten Wiltink
.
- Follow-Ups:
- Re: D2006 Object inspector component
- From: DoctorC
- Re: D2006 Object inspector component
- References:
- D2006 Object inspector component
- From: DoctorC
- Re: D2006 Object inspector component
- From: Rob Kennedy
- Re: D2006 Object inspector component
- From: DoctorC
- Re: D2006 Object inspector component
- From: Maarten Wiltink
- Re: D2006 Object inspector component
- From: DoctorC
- Re: D2006 Object inspector component
- From: Maarten Wiltink
- Re: D2006 Object inspector component
- From: DoctorC
- Re: D2006 Object inspector component
- From: Maarten Wiltink
- Re: D2006 Object inspector component
- From: DoctorC
- D2006 Object inspector component
- Prev by Date: Label with picture
- Next by Date: Re: D2006 Object inspector component
- Previous by thread: Re: D2006 Object inspector component
- Next by thread: Re: D2006 Object inspector component
- Index(es):
Relevant Pages
|