Board index » delphi » Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion


2007-06-19 07:50:02 PM
delphi191
Quote
It means disable.
When it goes away it is "deleted".
What purpose does it serve?
I mean, I rarely ever use the same breakpoint more than once...
Eric
 
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

I will quite often be using the same breakpoint for a parser
I've writen and go through the breakpoint several thousand
times. Once I have found the cause I will disable it and run at
full speed but I may well want the breakpoint again at a
later date. This is where a disabled breakpoint is useful.
It's also good as it is easier to find a disabled breakpoint
when it is a different colour from the rest of text/enabled
breakpoints.
Pete
"Eric Grange" <XXXX@XXXXX.COM>writes
Quote
>It means disable.
>When it goes away it is "deleted".

What purpose does it serve?
I mean, I rarely ever use the same breakpoint more than
once...

Eric
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

Eric Grange writes:
Quote
What purpose does it serve?
You don't lose all of your settings associated with the break point.
--
TJSDialog - TaskDialog for other operating systems:
www.jed-software.com/jsd.htm
Visual Forms IDE Add In: www.jed-software.com/vf.htm
Blog: jedqc.blogspot.com
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

Eric Grange writes:
Quote
On the bright side, I guess this helped with Delphi's own horribly
misaligned UI (a tour of the options dialog in Delphi 7 is like a tour of
UI misalignment and spacing issues f.i.).
Unfortunately that isn't true.
Actually it is so sad it is funny.
Check out the project options screenshot in attachments (SUBJ:
Misaligned options). I mean serious, what developer hands that over for
peer review. What reviewer doesn't smack the guy/gal on the back of the
head and tell him/her to line it up properly.
Brand new feature and a form designer that has pretty pink lines and
they still can not align things up properly.
It has improved though (alignments), but when new ones like this sneak
through, I wonder if they just do these types of things on purpose to
beef up the QC stats numbers.
--
TJSDialog - TaskDialog for other operating systems:
www.jed-software.com/jsd.htm
Visual Forms IDE Add In: www.jed-software.com/vf.htm
Blog: jedqc.blogspot.com
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

Quote
>It means disable.
>When it goes away it is "deleted".

What purpose does it serve?
I mean, I rarely ever use the same breakpoint more than once...
Well, the functionality is available from the Delphi 7 breakpoints dialog (it's
a checkbox) - in the editor, a disabled breakpoint gets painted green. So
making it a keystroke was a sensible thing to do, IMO.
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

Eric Grange writes:
Quote
You assume designer guidelines provide for a more time efficient
solution to consistent alignment and spacing, which remains to be
demonstrated.
They certainly are for me. Which is why I changed PC's to design my
form (mentioned earlier post).
I'm lost without them now ;-)
--
TJSDialog - TaskDialog for other operating systems:
www.jed-software.com/jsd.htm
Visual Forms IDE Add In: www.jed-software.com/vf.htm
Blog: jedqc.blogspot.com
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

Eric Grange writes:
Quote
TBH many Delphi
applications out there seem to have misalignment issues, despite
proper aligning being more easily achieved in them than in, say, MFC
apps, so I guess Delphi developpers have developped a certain
"immunity" and don't spot alignment/spacing issues so readily.
I believe this is a 'cultural' phenomenon - I do see a distinct
difference between US programs and French programs, GUI-wise. Not every
program by every programmer of course, but enough to feel like a trend.
To a Frenchman it seems just unthinkable to have a 'sloppy' UI, while
on the US side it is more like 'it works, what are you complaining
about?' (fast food ->fast programming ->no time for those small
adjustments?).
Or I have just been lucky with my French programs...
I haven't seen enough German programs to say anything about them, and
Swedish programs I see mostly my own,, so that is for someone else to
judge...
:-)
--
Anders Isaksson, Sweden
BlockCAD: web.telia.com/~u16122508/proglego.htm
Gallery: web.telia.com/~u16122508/gallery/index.htm
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

Quote
I will quite often be using the same breakpoint for a parser
I've writen and go through the breakpoint several thousand
times.
Funnily enough I am currently debugging a parser too, though I am not
proceeding in that manner. I usually place my breakpoints were they'll
be hit only once, and I rarely go bug hunting into the same lines of
code twice.
I've stopped placing breakpoints in loops or other multi-occuring code
locations long ago (too annoying to trace through, or enter conditions
to make relevant). Though I guess if you really heavily on breakpoint
conditions, a disable could be useful.
Personnally, I am not afraid of hitting low level disassembly and stack
views, so I have access to parameters/intermediate values the IDE itself
provides no info on. More often than not, a single well-placed
breakpoint (in the code that should be run, or in a "finally" section)
is sufficient to identify the bug in the first run.
Eric
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

Quote
You don't lose all of your settings associated with the break point.
I realized that when answering Pete. Had completely forgotten about them
since I never use them.
Eric
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

"Eric Grange" <XXXX@XXXXX.COM>writes
Quote
I'll stir the old pot: how about a Delphi 7 revival?
The new compiler, but with the old IDE, the old help. Nothing fancy: just
get the old source, replace with new RTL/VCL/Compiler and get it to run.
No need for the new code editor or whatever extras, if it needs .Net, or
if it needs too much conversion work, don't include it. Period. Keep
things simple and stable.
What would be the point? People who want the old IDE can use it right now.
No need for Codegear to waste resources on it. The new IDE is so much better
that it would be sheer stupidity for CodeGear to abandon it.
The only thing Delphi 7 did better was the help, and that is not an IDE thing
really.
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

Quote
What would be the point? People who want the old IDE can use it right now.
The old IDE yes, the new compiler, no.
Eric
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

Eric Grange writes:
Quote
>Not what you said, though.

I said "D7 has that, or maybe you mean something different?"
To which JED replied "No it doesn't"

Maybe you could post a clarification?
Ctrl+Shift+Up/Down arrow navigates between interface and implementation of
methods, not uses clause.
--
Wayne Niddery - Winwright, Inc (www.winwright.ca)
"Democracy, without the guarantee of liberty, is merely a method of
selecting tyrants." - Alan Nitikman
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

Quote
Ctrl+Shift+Up/Down arrow navigates between interface and implementation of
methods, not uses clause.
That's what they do in Delphi 7, yes.
You mean that in Delphi 2007 they also navigate between uses clauses? That's
nice, but I'd have hoped that by now it implemented what experts
gave me since D3, ie. the ability to reach both uses clauses from
anywhere in the code with shortcuts (here Ctrl+W 2 & 3).
Eric
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

"JED" <XXXX@XXXXX.COM>writes
Quote
>from 8 on that are 'must haves'. Heck, I didnt see any improvements
>that are even 'would use'.
- Sync Edit
- Ctrl+Shift+Up/Down arrow to navigate uses clause
- Ctrl+Click to disable a breakpoint
- Form Designer guidelines
- Ctrl+/ comment
- A big on that is shiploads better in the new IDE is package handling,
heck Ctrl+F9 didn't even compile packages in the "good" ole days.
- Tool Palette
- Tool Palette filtering
I hate the new tool palette, so thats a drawback for me, not a plus. And
the rest - well, a few extra ctrl-key combinations that I probably wouldnt
use do not offset the {*word*99}py help systems, slower IDE interface, and
absolutely rediculous runtime dependencies of D2007. (Not to mention that
D2007 WONT EVEN INSTALL on my main development machine because one of the
installers for one of the dependencies fails.).
 

Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion

GrandmasterB writes:
Quote
a few extra ctrl-key combinations that I probably wouldnt use
That is the same for most new features though. Once you start using
them you end up wondering how you lived without them
If you think they were the *only* enhancements then I suggest you look
at the articles Nick posted on CDN or DN. Whatever the official name
for that site is now days.
Quote
do not offset the {*word*99}py help systems,
I actually don't have an issue with the help system although I admit I
rarely use help.
Quote
slower IDE interface,
I find it easily acceptable when compared to Delphi 7 for the enhancements I
use.
Quote
and absolutely rediculous runtime dependencies of D2007.
I have no issues with this. It is what it is. Although I have all those
dependancies (except J# runtime) on my PC anyway.
--
TJSDialog - TaskDialog for other operating systems:
www.jed-software.com/jsd.htm
Visual Forms IDE Add In: www.jed-software.com/vf.htm
Blog: jedqc.blogspot.com