Does anyone use RichMemopack?
I got an error message
class function TRichEditManager.LoadRichText(RichEditWnd: Handle; ASrc: TStream): Boolean;
var
cbs : TEditStream_;
begin
cbs.dwCookie := PDWORD(ASrc);
cbs.dwError := 0;
cbs.pfnCallback := @RTFLoadCallback;
SendMessage(RichEditWnd, EM_STREAMIN, SF_RTF, LPARAM(@cbs) );
Result := cbs.dwError = 0;
end;
win32richmemoproc.pas(730,22) Error: Incompatible types: got "<address of function(PDWord;PByte;LongInt;var LongInt):DWord;StdCall>" expected "<procedure variable type of function(LongWord;PByte;LongInt;var LongInt):DWord;StdCall>"
Does anyone use RichMemopack?
I got an error message
class function TRichEditManager.LoadRichText(RichEditWnd: Handle; ASrc: TStream): Boolean;
var
cbs : TEditStream_;
begin
cbs.dwCookie := PDWORD(ASrc);
cbs.dwError := 0;
cbs.pfnCallback := @RTFLoadCallback;
SendMessage(RichEditWnd, EM_STREAMIN, SF_RTF, LPARAM(@cbs) );
Result := cbs.dwError = 0;
end;
win32richmemoproc.pas(730,22) Error: Incompatible types: got "<address of function(PDWord;PByte;LongInt;var LongInt):DWord;StdCall>" expected "<procedure variable type of function(LongWord;PByte;LongInt;var LongInt):DWord;StdCall>"
RichMemo has a github repository with issue tracking: https://github.com/skalogryz/richmemo/.
Probably best to report the issue there. Or, start a separate thread.
Is there a workaround available?
Is there a workaround available?
Did you by any chance not do a clean reinstallation? Meaning you removed the old Lazarus and installed the new one? Cause from 2.0.x to 2.2 some units were moved to a different package, but the compiled units would remain of course if you didn't remove the old installation. As a workaround you can remove all files inside /Applications/Lazarus/components/buildintf/units/x86_64-darwin.
Though it might be a good idea that the installer does a cleanup by itself, to avoid such problems in the future...
Thanks, but this didn't solve the problem.
Thanks, but this didn't solve the problem.
I meant /Applications/Lazarus/components/ideintf/units/x86_64-darwin, sorry... (cause the units were moved from IDEIntf to BuildIntf)
@jwdietrich, please start a new thread about you compilation problems in a proper section. This is a release announcement thread.
Hello. I have problems with version 2.2.0. When I open my projects made with version 2.0.12 and I try to add a new form it doesn't let me. I get the following error when trying to save the new form.
Could not set flowForm1: TForm1.
Abstract method called
I have tested it on Ubuntu 20.04 and Windows 11.
Does anyone know how to solve that? Or should I redo all my old projects.
Is there a guide how to update an existing Lazarus 2.0.12/FPC 3.2.0 installation to the new versions? I do have some projects which currently use the old lazarus version. These project should be updated too..
Hello. I have problems with version 2.2.0. When I open my projects made with version 2.0.12 and I try to add a new form it doesn't let me. I get the following error when trying to save the new form.
Could not set flowForm1: TForm1.
Abstract method called
I have tested it on Ubuntu 20.04 and Windows 11.
Does anyone know how to solve that? Or should I redo all my old projects.
Can you start Lazarus (on Linux) from a console, and see if it prints any form of stack dump?
( On windows: lazarus --debug-log=C:\lazlog.txt )
If you do get a dump, but no line numbers, then please rebuild (Tools menu) the IDE with "configure build lazarus" and specify -gl -gw -O-1
Also chose the "clean build" radio item.
Then check again for the stack dump.
Unfortunately the stack does not help....
Do you have any packages installed into your IDE?
(If you have not yet, please try a "clean" rebuild of the IDE.)
Is there a way this can be reproduced?
Can the project be send (in private and confidentially, if needed)?
The error seems to be with the "xmlresource" package. When installing it begins to fail. This time I did not install it in Ubuntu and everything works normal. I uninstalled it in Windows 11 and had no more problems.
@Martin_fr,
I have repro with "xmlresource" package, I will post the bug report.
Done
https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39538
unfortunately the debug do not allow me to step in the procedure (as I put a breakpoint Lazarus show it as unreachable)
I know,
I try to replicate with a minimum amount of code but it works.
I have a component inherited from TDOSComand that I found in www.torry.net.
My component just call inherited in the destroy. The destroy in TDOSComand is
unfortunately the debug do not allow me to step in the procedure (as I put a breakpoint Lazarus show it as unreachable)
Hello,I know,
I try to replicate with a minimum amount of code but it works.
I have a component inherited from TDOSComand that I found in www.torry.net.
My component just call inherited in the destroy. The destroy in TDOSComand is
unfortunately the debug do not allow me to step in the procedure (as I put a breakpoint Lazarus show it as unreachable)
it seems that it is the debugger on 2.2 version of lazarus that causes the problem :
no problem with version 2.0.12 when exiting a doscommand test program.
no problem when exiting a doscommand test program without debug in 2.2 version of Lazarus.
Access violation when exiting a doscommand test program with debug in 2.2 version of Lazarus (see attachment).
Friendly, J.P
Hello,I know,
I try to replicate with a minimum amount of code but it works.
I have a component inherited from TDOSComand that I found in www.torry.net.
My component just call inherited in the destroy. The destroy in TDOSComand is
unfortunately the debug do not allow me to step in the procedure (as I put a breakpoint Lazarus show it as unreachable)
it seems that it is the debugger on 2.2 version of lazarus that causes the problem :
no problem with version 2.0.12 when exiting a doscommand test program.
no problem when exiting a doscommand test program without debug in 2.2 version of Lazarus.
Access violation when exiting a doscommand test program with debug in 2.2 version of Lazarus (see attachment).
Friendly, J.P
the access violation comes with the terminate of the FThread :
With this code no more problem :
It looks like I'm the only one with this trouble.
Project > New Project > Run > Image related.
It can't run my old projects too. I can't run anything.
I've updated it from Lazarus 2.0.12.
What did I do wrong?
'Change Class' not working in 2.2.0...? Whatever I choose, it just doesn't do anything - no errors, just nothing. Any setting I am missing...?Cannot confirm with Windows 11 and out-of-the-box settings.
Hello,I know,
I try to replicate with a minimum amount of code but it works.
I have a component inherited from TDOSComand that I found in www.torry.net.
My component just call inherited in the destroy. The destroy in TDOSComand is
unfortunately the debug do not allow me to step in the procedure (as I put a breakpoint Lazarus show it as unreachable)
it seems that it is the debugger on 2.2 version of lazarus that causes the problem :
no problem with version 2.0.12 when exiting a doscommand test program.
no problem when exiting a doscommand test program without debug in 2.2 version of Lazarus.
Access violation when exiting a doscommand test program with debug in 2.2 version of Lazarus (see attachment).
Friendly, J.P
it seems that it is the debugger on 2.2 version of lazarus that causes the problem :
no problem with version 2.0.12 when exiting a doscommand test program.
no problem when exiting a doscommand test program without debug in 2.2 version of Lazarus.
Access violation when exiting a doscommand test program with debug in 2.2 version of Lazarus (see attachment).
Don't waste your time for this ( and also mine ;) ), it is not sure that it is a bug, may be the doscommand has a wrong way to terminate the thread.it seems that it is the debugger on 2.2 version of lazarus that causes the problem :
no problem with version 2.0.12 when exiting a doscommand test program.
no problem when exiting a doscommand test program without debug in 2.2 version of Lazarus.
Access violation when exiting a doscommand test program with debug in 2.2 version of Lazarus (see attachment).
Do you have a sample that reproduces the issue (including copy of the DosCommand package you use (if that is open source / can be shared).
Target 32 bit?
Debugged from within a 64 or 32bit IDE ?
=> If you have, then please create an issue in the bug tracker.