1
General / Re: JEDI error but unit compiles??
« Last post by Thaddy on Today at 09:30:33 pm »tnx
I agree, "trick" isn't really a good description but, I can't think of a good one at this time. "options" maybe ?QuoteFor instance the trick about "@textvar[0]" to not have every character individually enclosed in single quotes is quite usefulWhile it might be worth advertising, I wouldn't name it a "trick".
It is normal pascal syntax. You simply watch an expression that returns a "pchar" => so you get to see a pchar. (which is displayed as string)
Maybe you can open a new topic on that (and moderate the topic), and see what others think.I intend to do that. Hopefully today or tomorrow.
In general, the debugger has tons of features that are probably seldom used.I think the real challenge is in figuring out which features are seldom used because they are seldom needed compared to which features are seldom used because they are not common knowledge, e.g, the construct "Ptr[a..b]" is logical but, I didn't know about it and I wouldn't have thought of using it because it's not a valid Pascal statement. Constructions like that are debugging pearls, extremely useful.
I have other forms that the JvDBLoopUpCombo isn't displaying the 2nd or 3rd fields in the drop-down to fix these.As I wrote above, the DisplayWidth specified for a field is interpreted by TJvDBLookupCombo as the width of the same count of 'M' characters. This is required because nowadays fonts have non-uniform character widths; otherwise the column edge would be jagged. Since 'M' is a relatively wide character a DisplayWidth of, say, 10 may appear much wider than you anticipate for your real field values which maybe contain a lot of narrow characters, such as i, l, or r. Please repeat your tests after switching the JvDBLookupCombo's font to Courier or another non-proportional font.
Thanks ASerge; tried -– true. But, do one see also the causes here? Hm.TDateTimePicker uses a nested form for the calendar.