Re: [Lazarus] 68K

2011-09-15 Thread Michael Schnell
On 09/14/2011 03:50 PM, Martin Schreiber wrote: Is it possible/viable to use the Lazarus IDE for writing and compiling the code ? Is it possible to configure the Lazarus IDE to use gdb in cross-mode ? Maybe you should have a look to MSEide too. MSEide has been designed not only for MSEgui /

Re: [Lazarus] 68K

2011-09-15 Thread Michael Schnell
On 09/14/2011 04:37 PM, Sven Barth wrote: You need to use a pre 2.0 version of FPC for this. The 68k code isn't enabled and/or maintained in current versions. Of course you can try to revive it again :D Seems viable- What is the reason why 68K is not supported in the newer versions ?

Re: [Lazarus] 68K

2011-09-15 Thread Mark Morgan Lloyd
Michael Schnell wrote: On 09/14/2011 03:50 PM, Martin Schreiber wrote: Is it possible/viable to use the Lazarus IDE for writing and compiling the code ? Is it possible to configure the Lazarus IDE to use gdb in cross-mode ? Maybe you should have a look to MSEide too. MSEide has been

Re: [Lazarus] 68K

2011-09-15 Thread Mark Morgan Lloyd
Michael Schnell wrote: On 09/14/2011 04:37 PM, Sven Barth wrote: You need to use a pre 2.0 version of FPC for this. The 68k code isn't enabled and/or maintained in current versions. Of course you can try to revive it again :D Seems viable- What is the reason why 68K is not supported in

Re: [Lazarus] 68K

2011-09-15 Thread Felipe Monteiro de Carvalho
On Thu, Sep 15, 2011 at 10:01 AM, Michael Schnell mschn...@lumino.de wrote: What is the reason why 68K is not supported in the newer versions ? zero contributors and zero maintainers for such a port. Just the same reason for every other missing feature. -- Felipe Monteiro de Carvalho --

Re: [Lazarus] 68K

2011-09-15 Thread Michael Schnell
On 09/15/2011 11:25 AM, Mark Morgan Lloyd wrote: ... Thanks for the pointers In any event please write up what you do for the wiki to get it into the record. Of course I'll be posting here when starting this :-) . -Michael -- ___ Lazarus

Re: [Lazarus] lazarus debug with gdb [Re: [fpc-devel] bounty: FPC based debugger]

2011-09-15 Thread Martin
On 15/09/2011 10:33, Graeme Geldenhuys wrote: On 14/09/2011 22:06, Martin wrote: while ansistring pose a general problem, using shhotstring, stabs does the job. (fpc trunk / gdb 7.3-2 / win 32) VarString15 starts with T15 -data-evaluate-expression VarString15[2] STABS: ^done,value=49 '1'

Re: [Lazarus] 68K

2011-09-15 Thread Michael Schnell
On 09/15/2011 10:28 AM, Mark Morgan Lloyd wrote: Michael Schnell wrote: On 09/14/2011 04:37 PM, Sven Barth wrote: You need to use a pre 2.0 version of FPC for this. The 68k code isn't enabled and/or maintained in current versions. Of course you can try to revive it again :D Seems viable-

Re: [Lazarus] lazarus debug with gdb [Re: [fpc-devel] bounty: FPC based debugger]

2011-09-15 Thread Graeme Geldenhuys
On 15/09/2011 11:50, Martin wrote: By now, you should know the can-do and con-not-do, and you should be able to use accordingly. (e.g. watch the entire string, instead of an index / or add 1 to the index yourself) At the time I reported the inconsistency problem, I used Lazarus IDE for

Re: [Lazarus] lazarus debug with gdb [Re: [fpc-devel] bounty: FPC based debugger]

2011-09-15 Thread Martin
On 15/09/2011 11:00, Graeme Geldenhuys wrote: On 15/09/2011 11:50, Martin wrote: By now, you should know the can-do and con-not-do, and you should be able to use accordingly. (e.g. watch the entire string, instead of an index / or add 1 to the index yourself) At the time I reported the

Re: [Lazarus] 68K

2011-09-15 Thread Mark Morgan Lloyd
Michael Schnell wrote: On 09/15/2011 11:25 AM, Mark Morgan Lloyd wrote: ... Thanks for the pointers In any event please write up what you do for the wiki to get it into the record. Of course I'll be posting here when starting this :-) . I've added a stub to

[Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Graeme Geldenhuys
Hi, The spaces inside Comments or Compiler Directives are not the correct color compared to spaces inside code. So when you set the foreground color of Space characters, that color is not applied inside Comments or Compiler Directives. Thus making things like Comments especially hard to read.

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Martin
On 15/09/2011 12:48, Graeme Geldenhuys wrote: Hi, The spaces inside Comments or Compiler Directives are not the correct color compared to spaces inside code. So when you set the foreground color of Space characters, that color is not applied inside Comments or Compiler Directives. Thus making

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Martin
On 15/09/2011 12:59, Martin wrote: On 15/09/2011 12:48, Graeme Geldenhuys wrote: Hi, The spaces inside Comments or Compiler Directives are not the correct color compared to spaces inside code. So when you set the foreground color of Space characters, that color is not applied inside Comments

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Graeme Geldenhuys
On 15/09/2011 13:59, Martin wrote: what about spaces in strings? They suffer the same problem. This would be a nice to have - see comment below. I probably fix it for comment, but comments only. Comments have far more words in the text that strings in my code. So I'll be perfectly happy

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Graeme Geldenhuys
On 15/09/2011 14:03, Martin wrote: I only want the scanner to do that if the result is needed. otherwise the structural scan suffers from slow down I guess one could look at the Editor Settings (is show special characters enabled) and if so, is Text foreground color non-default, then only

Re: [Lazarus] Editor and usage of Tab characters

2011-09-15 Thread Martin
On 15/09/2011 12:29, Graeme Geldenhuys wrote: Hi, I'm a bit confused about the Source Editor settings, and the actual behaviour of Tabs in the editor. I switched one project from Spaces to Tabs to try it out indenting a single line by using the Tab key works correctly. As you can see in the

Re: [Lazarus] Editor and usage of Tab characters

2011-09-15 Thread Graeme Geldenhuys
On 15/09/2011 14:14, Martin wrote: Yep that needs to be implemented. Thanks. Reported in Mantis. http://bugs.freepascal.org/view.php?id=20256 the block indent type (despite the name) currently refers to what happesn if you press return (and if you use the editors, not codetools

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Martin
On 15/09/2011 13:10, Graeme Geldenhuys wrote: On 15/09/2011 14:03, Martin wrote: I only want the scanner to do that if the result is needed. otherwise the structural scan suffers from slow down I guess one could look at the Editor Settings (is show special characters enabled) and if so, is

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Martin
On 15/09/2011 13:08, Graeme Geldenhuys wrote: On 15/09/2011 13:59, Martin wrote: what about spaces in strings? They suffer the same problem. This would be a nice to have - see comment below. I probably fix it for comment, but comments only. Comments have far more words in the text that

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Flávio Etrusco
On Thu, Sep 15, 2011 at 9:26 AM, Martin laza...@mfriebe.de wrote: On 15/09/2011 13:08, Graeme Geldenhuys wrote: On 15/09/2011 13:59, Martin wrote: what about spaces in strings? They suffer the same problem. This would be a nice to have - see comment below. I probably fix it for comment,

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Graeme Geldenhuys
On 15/09/2011 14:26, Martin wrote: If someone setting to highlight comment or string is by underlining, then a continuous underline should be expected. I guess. :) I must add, I really like the look of Bold+Italic spaces. ;-) Regards, - Graeme - -- fpGUI Toolkit - a cross-platform

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Martin
On 15/09/2011 13:42, Graeme Geldenhuys wrote: On 15/09/2011 14:26, Martin wrote: If someone setting to highlight comment or string is by underlining, then a continuous underline should be expected. I guess. :) I must add, I really like the look of Bold+Italic spaces. ;-) All a question of

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Martin
On 15/09/2011 13:43, Flávio Etrusco wrote: On Thu, Sep 15, 2011 at 9:26 AM, Martinlaza...@mfriebe.de wrote: On 15/09/2011 13:08, Graeme Geldenhuys wrote: On 15/09/2011 13:59, Martin wrote: what about spaces in strings? They suffer the same problem. This would be a nice to have - see comment

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Graeme Geldenhuys
On 15/09/2011 14:50, Martin wrote: If I understand this right, it would make comment background color stop working? good point Umm... then what if the special characters is always rendered using the same foreground color as setup for Comments - just a bit darker or light than the original

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Martin
On 15/09/2011 14:32, Graeme Geldenhuys wrote: On 15/09/2011 14:50, Martin wrote: If I understand this right, it would make comment background color stop working? good point Umm... then what if the special characters is always rendered using the same foreground color as setup for Comments -

Re: [Lazarus] SynEdit and gutter behaviour

2011-09-15 Thread Bart
On 9/15/11, Martin laza...@mfriebe.de wrote: If you wish to change text by code (from your app, rather than user input), then you do not necessarily want to have to select the to-be-changed-text first. I understood you incorrectly then. It is the user that selects text, then clicks a button

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Graeme Geldenhuys
On 15/09/2011 15:51, Martin wrote: --- I do like 1, for the problem at hand, spaces in comment may still be blue-ish (or whatever your setting, but faded to background +1 I like your option (1) as well. Comments will still look like comments - unlike my color scheme where comments are

Re: [Lazarus] lazarus debug with gdb [Re: [fpc-devel] bounty: FPC based debugger]

2011-09-15 Thread Joost van der Sluis
On Thu, 2011-09-15 at 11:33 +0200, Graeme Geldenhuys wrote: On 14/09/2011 22:06, Martin wrote: while ansistring pose a general problem, using shhotstring, stabs does the job. (fpc trunk / gdb 7.3-2 / win 32) VarString15 starts with T15 -data-evaluate-expression VarString15[2]

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-15 Thread Joost van der Sluis
On Tue, 2011-09-13 at 23:28 +0200, Graeme Geldenhuys wrote: On 13 September 2011 22:18, Joost van der Sluis wrote: Funny how experiences can differ. I honestly can't think how anybody can say Lazarus debugging is better than Delphi (or even Kylix 3 from years ago). But as you said, each

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-15 Thread Martin
On 15/09/2011 18:00, Joost van der Sluis wrote: On Tue, 2011-09-13 at 23:28 +0200, Graeme Geldenhuys wrote: better than with Delphi. That's because when you're debugging on Delphi, the IDE is scaled down to the feature-level of Notepad. Normal code navigation (Ctrl+Click) in Delphi 7 [only

Re: [Lazarus] 68K

2011-09-15 Thread Marco van de Voort
On Thu, Sep 15, 2011 at 10:03:07AM +0200, Michael Schnell wrote: On 09/14/2011 06:32 PM, Mark Morgan Lloyd wrote: Does that also apply to cross builds? Could Lazarus built with a current FPC drive a 1.x compiler, or is it too different? I don't think I would need to do that. I suppose I

Re: [Lazarus] 68K

2011-09-15 Thread Marco van de Voort
On Thu, Sep 15, 2011 at 08:28:16AM +, Mark Morgan Lloyd wrote: enabled and/or maintained in current versions. Of course you can try to revive it again :D Seems viable- What is the reason why 68K is not supported in the newer versions ? Demand? I think this thread is the first

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-15 Thread Rich Saunders
On 9/15/11 1:21 PM, Martin wrote: That means the way they implemented their feature is extremely inconsistent: 1) in Delphi you are not supposed to edit source wile debugging 2) If inserting lines, in source while debugging (like in Lazarus) Delphi keeps track of line positions, so the

Re: [Lazarus] Is there a timer component that can be placed on data module?

2011-09-15 Thread Frank Church
On 15 September 2011 15:59, Frank Church vfcli...@gmail.com wrote: Is there a timer component that can be placed on a data module? I just revisited a form I developed earlier wondering why I didn't use a data module for it and realized that the data modules don't accept the TTimer component?

Re: [Lazarus] 68K

2011-09-15 Thread Sven Barth
On 15.09.2011 19:47, Marco van de Voort wrote: On Thu, Sep 15, 2011 at 08:28:16AM +, Mark Morgan Lloyd wrote: I see that the Linux kernel still supports the architecture, and that Qemu supports a variant. But I don't think I've ever seen a 68K system on e.g. eBay... I lie, somebody was

Re: [Lazarus] debug hints in lazarus [Re: [fpc-devel] Status and ideas about debug info (stabs, dwarf / dwar3)]

2011-09-15 Thread Graeme Geldenhuys
On 15 September 2011 19:21, Martin wrote: 1) in Delphi you are not supposed to edit source wile debugging I believe that is their theory, because even in Delphi 7 there is a option to make all edit buffers read-only when debugging is started. -- Regards,   - Graeme -

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Flávio Etrusco
Is there some special chars On Thu, Sep 15, 2011 at 11:00 AM, Graeme Geldenhuys graemeg.li...@gmail.com wrote: On 15/09/2011 15:51, Martin wrote: --- I do like 1, for the problem at hand, spaces in comment may still be blue-ish (or whatever your setting, but faded to background +1 I like

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Martin
On 15/09/2011 22:34, Flávio Etrusco wrote: Is there a SynAttribute for special chars? BTW in SynEdit I had a long-live TO-DO to allow only showing Tab chars (and maybe linebreaks) ;-) eoShowSpecialChars in SynEdit.Options ? yea, selecting which special chars would be nice too --

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Flávio Etrusco
On Thu, Sep 15, 2011 at 6:39 PM, Martin laza...@mfriebe.de wrote: On 15/09/2011 22:34, Flávio Etrusco wrote: Is there a SynAttribute for special chars? BTW in SynEdit I had a long-live TO-DO to allow only showing Tab chars (and maybe linebreaks) ;-) eoShowSpecialChars in SynEdit.Options ?

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Martin
On 15/09/2011 22:50, Flávio Etrusco wrote: On Thu, Sep 15, 2011 at 6:39 PM, Martinlaza...@mfriebe.de wrote: On 15/09/2011 22:34, Flávio Etrusco wrote: Is there a SynAttribute for special chars? BTW in SynEdit I had a long-live TO-DO to allow only showing Tab chars (and maybe linebreaks) ;-)

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Martin
On 15/09/2011 23:07, Martin wrote: On 15/09/2011 22:50, Flávio Etrusco wrote: On Thu, Sep 15, 2011 at 6:39 PM, Martinlaza...@mfriebe.de wrote: On 15/09/2011 22:34, Flávio Etrusco wrote: Is there a SynAttribute for special chars? BTW in SynEdit I had a long-live TO-DO to allow only showing

Re: [Lazarus] Database Library Issues

2011-09-15 Thread Terry A. Haimann
On 09/14/2011 03:43 PM, Mark Morgan Lloyd wrote: leledumbo wrote: Aparently, Lazarus is looking for libpq.so.4, while my implementations have libpq.so.5 It shouldn't be hardcoded AFAIK: libpq.so only, which may be a symlink to the correct version. Try checking the source code whether the .4

Re: [Lazarus] The color of special characters in the Source Editor

2011-09-15 Thread Paul Ishenin
15.09.2011 20:03, Martin wrote: I probably fix it for comment, but comments only. Comments should stay comments. Space in a commect is not the same as a space in other parts of code. If I were you I would not implement it at all. The only missing thing for comments is a spell checker.