Recent

Author Topic: events in object inspector  (Read 697 times)

ravkepar

  • Newbie
  • Posts: 5
events in object inspector
« on: June 08, 2025, 10:28:24 pm »
Has anyone had the following problem with version 4.0?
When I 'm double clicking on the events in the object inspector, the IDE blocks and doesn't go to the proper procedure.  :-\
I'm using a Mac Mini M4 withe the latest MacOS and Lazarus 4.0.
I didn't had this problem with earlier versions of Lazarus...  ::)
« Last Edit: June 08, 2025, 10:30:09 pm by ravkepar »

n7800

  • Sr. Member
  • ****
  • Posts: 394
Re: events in object inspector
« Reply #1 on: June 08, 2025, 10:32:51 pm »
Are you using the "DockedFormEditor" or "AnchorDockingDsgn" packages?

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 11440
  • Debugger - SynEdit - and more
    • wiki
Re: events in object inspector
« Reply #2 on: June 08, 2025, 11:28:21 pm »
the IDE blocks and doesn't go to the proper procedure

1) "blocks" => as in "hang"? I.e. it stops responding to any input, and you have to kill it? No, I have not had that.
2) Or "blocks" => as in, takes a few seconds...
3) Or just "doesn't go to the proper procedure" ?

If 2 or 3: Is there an error message in the messages window? (You may have to open it, bring it to front)

If 2: Start it from console, and check if there is any console output.



In any case: Make sure your project compiles. If it doesn't then the IDE may not be able to find the procedure...

Can you navigate in code (go to declaration)?
Can you code complete (e.g. create new procedures in the class or create local vars)?

Also from menu Tools > rescan fpc directory
(just in case).


ravkepar

  • Newbie
  • Posts: 5
Re: events in object inspector
« Reply #3 on: June 09, 2025, 09:55:10 am »
The system says "not responding" program (Lazarus) and I have to kill Lazarus and restart it.
The installation was standard, so no extra units, etc installed.
No message, just lazarus stops working...
Compilation works. I just can't double click in the event window in the object inspector to go to the proper procedure.

ravkepar

  • Newbie
  • Posts: 5
Re: events in object inspector
« Reply #4 on: June 09, 2025, 09:56:02 am »
Are you using the "DockedFormEditor" or "AnchorDockingDsgn" packages?
not that I know of...

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 11440
  • Debugger - SynEdit - and more
    • wiki
Re: events in object inspector
« Reply #5 on: June 09, 2025, 10:12:33 am »
The system says "not responding" program (Lazarus) and I have to kill Lazarus and restart it.

Ok, so indeed "blocks"...

Open a terminal (terminal of your choice, e.g. gnome-terminal). In the shell (of the terminal) "cd" to the lazarus dir. Then run lazarus. Now get it to "block", and see if there is any output in the terminal (maybe some exception, and addresses, or linenumbers?)

If there is none, then you can stop lazarus with ctrl-c

Run
gdb -ex r lazarus

when it blocks hit ctrl-c
then enter (and follow by return)
   bt

and copy the output.

If it is only addresses, then it may need some more steps to get some useful info.


n7800

  • Sr. Member
  • ****
  • Posts: 394
Re: events in object inspector
« Reply #6 on: June 09, 2025, 08:25:48 pm »
Are you using the "DockedFormEditor" or "AnchorDockingDsgn" packages?
not that I know of...

You seem unsure? For your information, one is used to dock IDE windows, and the other is used to dock the Designer window with the Source Editor window.

In Lazarus 4.0 they are installed by default. If it is not too much trouble, check if they are in the list of installed packages "Main Menu > Package > Install/Uninstall packages".

If they are installed, try to remove them for a while. Select them in the list on the left and click "Uninstall selection", then "Rebuild IDE". Check if the problem persists.

You can later return these packages through the same window.

ravkepar

  • Newbie
  • Posts: 5
Re: events in object inspector
« Reply #7 on: June 13, 2025, 11:13:26 pm »
The system says "not responding" program (Lazarus) and I have to kill Lazarus and restart it.

Ok, so indeed "blocks"...

Open a terminal (terminal of your choice, e.g. gnome-terminal). In the shell (of the terminal) "cd" to the lazarus dir. Then run lazarus. Now get it to "block", and see if there is any output in the terminal (maybe some exception, and addresses, or linenumbers?)

If there is none, then you can stop lazarus with ctrl-c

Run
gdb -ex r lazarus

when it blocks hit ctrl-c
then enter (and follow by return)
   bt

and copy the output.

If it is only addresses, then it may need some more steps to get some useful info.


Maybe I can send here a textfile with the error message and system info that is generated by MacOS?

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 11440
  • Debugger - SynEdit - and more
    • wiki
Re: events in object inspector
« Reply #8 on: June 14, 2025, 12:54:07 am »
Maybe I can send here a textfile with the error message and system info that is generated by MacOS?

Yes, might be a start.
If it helps I can only tell once I looked at it.

 

TinyPortal © 2005-2018