Board index » delphi » Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion
Eric Grange
![]() Delphi Developer |
Eric Grange
![]() Delphi Developer |
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion2007-06-19 07:50:02 PM delphi191 QuoteIt means disable. Eric |
Pete Fraser
![]() Delphi Developer |
2007-06-19 07:59:12 PM
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. |
JED
![]() Delphi Developer |
2007-06-19 08:07:14 PM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion
Eric Grange writes:
QuoteWhat purpose does it serve? 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 |
JED
![]() Delphi Developer |
2007-06-19 08:11:13 PM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion
Eric Grange writes:
QuoteOn the bright side, I guess this helped with Delphi's own horribly 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 |
Chris Rolliston
![]() Delphi Developer |
2007-06-19 08:12:07 PM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestionQuote>It means disable. making it a keystroke was a sensible thing to do, IMO. |
JED
![]() Delphi Developer |
2007-06-19 08:12:41 PM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion
Eric Grange writes:
QuoteYou assume designer guidelines provide for a more time efficient 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 |
Anders Isaksson
![]() Delphi Developer |
2007-06-19 08:25:16 PM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion
Eric Grange writes:
QuoteTBH many Delphi 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 |
Eric Grange
![]() Delphi Developer |
2007-06-19 08:26:07 PM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestionQuoteI will quite often be using the same breakpoint for a parser 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 |
Eric Grange
![]() Delphi Developer |
2007-06-19 08:26:58 PM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestionQuoteYou don't lose all of your settings associated with the break point. Eric |
John Jacobson
![]() Delphi Developer |
2007-06-19 10:45:02 PM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion
"Eric Grange" <XXXX@XXXXX.COM>writes
QuoteI'll stir the old pot: how about a Delphi 7 revival? 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. |
Eric Grange
![]() Delphi Developer |
2007-06-20 12:54:14 AM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestionQuoteWhat would be the point? People who want the old IDE can use it right now. |
Wayne Niddery [TeamB]
![]() Delphi Developer |
2007-06-20 12:58:45 AM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion
Eric Grange writes:
Quote>Not what you said, though. -- Wayne Niddery - Winwright, Inc (www.winwright.ca) "Democracy, without the guarantee of liberty, is merely a method of selecting tyrants." - Alan Nitikman |
Eric Grange
![]() Delphi Developer |
2007-06-20 01:05:27 AM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestionQuoteCtrl+Shift+Up/Down arrow navigates between interface and implementation of 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 |
GrandmasterB
![]() Delphi Developer |
2007-06-20 01:57:06 AM
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 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.). |
JED
![]() Delphi Developer |
2007-06-20 06:32:36 AM
Re: Delphi 7 revival? stirring the old pot + Delphi 64 suggestion
GrandmasterB writes:
Quotea few extra ctrl-key combinations that I probably wouldnt use 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. Quotedo not offset the {*word*99}py help systems, Quoteslower IDE interface, Quoteand absolutely rediculous runtime dependencies of D2007. -- 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 |