Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2002-02

Some more Bugs

4 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Mattias Gaertner
to Jens Arm: Hi Some more not correct working things: 1. If you click after a File/Close or if you…
Show quoted text 9 lines
Hi Some more not correct working things: 1. If you click after a File/Close or if you have choosen a Program/Project in the DownArrow of the ObjectInspector-Combo and then move the mouse into the Textarea of the Combo (where still Form1 is standing) then you get a pretty SegFault. You can try to typ some text in the combo-Textfield, too, then you get a SegFault, too :(

Form editing ... added to my bug list.

2. The chooseable editor-shortcuts should be attuned with the shown menu-shortcuts

already mentioned.

3. The Compiler-Message-Window is always hidden through the editor Could the messages not be integrated into the editor as a second section like in Delphi?

Delphi uses docking. Since gtk can also do that, we should try to get add docking into the lcl.

4. Where is the output of the running program (if you run over run/run) visible? There should be s.th. like an outputwindows, where it is possible to input things, if the running prog want some input.

That's right. At least for windows.
For linux I would like to see the output in the users favourite terminal.

Show quoted text 5 lines
5. The Editor-Options on the General-Tab (I have only tested with No Caret/No selection and Bracked Highlight options) are set to the default values if you open the Dialog a second time. You see that if you look into the generated XML-File, the checkboxes are OK, but not the file.

fixed.

6. A menu-Seperator between "Build all"/"run" would be nice. (looks better I think)

Agreed.

7. Which parts of the Debugger work and which not ?
Marc Weustink wrote 5 lines
Breakpoints aren't activated in the debugger yet (they are created in the IDE, the debugger object, but not in the actual debugger :) Step and step into should work (if you configured the IDE to use the GDB debugger).
A question: Where can I get RPMs of the FPC 1.1-Beta? I can't generate my own RPMs. I get if I try it many errors.

This is a question for the fpc-pascal list.
1 month ago, I was able to compile lazarus with fpc 1.1, but the IDE crashes with an AV.

Mattias

Reply by email

Jens Arm
to Mattias Gaertner
Show quoted text 12 lines
> > A question: > > Where can I get RPMs of the FPC 1.1-Beta? > > I can't generate my own RPMs. I get if I try it > > many errors. > > This is a question for the fpc-pascal list. 1 month ago, I was able to > compile lazarus with fpc 1.1, but the IDE crashes with an AV. There are no RPMs of that. There are TGZ binary packages generated dialy, but RPMs are only generated for releases. I'd advise to start using CVS and compile your own bins (and not using RPM)

Yes, I have used cvs since some time, but it is difficult to switch often between 1.0.5 for LAZARUS and the new 1.1 to test, if you use TGZs. With RPM you can switch very quick by removing and installing the old or new RPM.

Jens

Reply by email

Jens Arm

Hi

Some more not correct working things:
1. If you click after a File/Close or if you have choosen a Program/Project in the DownArrow of the ObjectInspector-Combo and then move the mouse into the Textarea of the Combo (where still Form1 is standing) then you get a pretty SegFault. You can try to typ some text in the combo-Textfield, too, then you get a SegFault, too :(
2. The chooseable editor-shortcuts should be attuned with the shown menu-shortcuts
3. The Compiler-Message-Window is always hidden through the editor Could the messages not be integrated into the editor as a second section like in Delphi?
4. Where is the output of the running program (if you run over run/run) visible? There should be s.th. like an outputwindows, where it is possible to input things, if the running prog want some input.
5. The Editor-Options on the General-Tab (I have only tested with No Caret/No selection and Bracked Highlight options) are set to the default values if you open the Dialog a second time.
You see that if you look into the generated XML-File, the checkboxes are OK, but not the file.
6. A menu-Seperator between "Build all"/"run" would be nice. (looks better I think)
7. Which parts of the Debugger work and which not ?

A question:
Where can I get RPMs of the FPC 1.1-Beta?
I can't generate my own RPMs. I get if I try it
many errors.

Jens

Reply by email

Marco van de Voort
to Mattias Gaertner: On Wed, 20 Feb 2002 16:43:23 +0100 Form editing ... added to my bug list. already…
Show quoted text 7 lines
> A question: > Where can I get RPMs of the FPC 1.1-Beta? > I can't generate my own RPMs. I get if I try it > many errors. This is a question for the fpc-pascal list. 1 month ago, I was able to compile lazarus with fpc 1.1, but the IDE crashes with an AV.

There are no RPMs of that. There are TGZ binary packages generated dialy, but RPMs are only generated for releases.

I'd advise to start using CVS and compile your own bins (and not using RPM)

Reply by email