I have a strange thing : with the project ziptest (attachment of this bugtracker post 0032773: paszlib inflate of file gives crc error (https://bugs.freepascal.org/view.php?id=32773) ) i cant'see the form and when i execute it no window displayed
Great work, but the release notes haven't been released yet ;)Which url have you looked at?
"Lazarus 1.8.0 is not yet released. This page is under construction!"
Open the lfm, and look at "Left"...
At least for me this is displayed way outside the visible desktop area.
Edit left to something reasonable, and it works.
Is there a page with known bugs per Lazarus/FPC version?Known bugs and issues are in bug tracker. There are thousands of them. It is unrealistic to copy them all to wiki or to release notes.
In this version Lazarus 1.8 the FormatFloat() error is still present.FPC release cycle is slow. The fix will not be in a release anytime soon.
See: http://forum.lazarus.freepascal.org/index.php/topic,39144.msg267614.html
In this version Lazarus 1.8 the FormatFloat() error is still present.
See: http://forum.lazarus.freepascal.org/index.php/topic,39144.msg267614.html (http://forum.lazarus.freepascal.org/index.php/topic,39144.msg267614.html)
With such a bug Lazarus 1.8 doesn't seem ready for production use and a (wiki-)page to list all known problems could help people decide if switching to that version is wise.
I understand. But it isn't easy to let the bugtracker show the bugs for just the Lazarus release 1.8.Is there a page with known bugs per Lazarus/FPC version?Known bugs and issues are in bug tracker. There are thousands of them. It is unrealistic to copy them all to wiki or to release notes.
Make Debuger output better.
Debuger Output on Arrays sometimes isterriblenot as aspected.
Properties can't be shown.
Check your fpc.cfg
usr/bin/ld: /usr/lib64/fpc/3.0.4/units/x86_64-linux/rtl/cprt0.o: нераспознанное перемещение (0x2a) в разделе «.text»
/usr/bin/ld: final link failed: Некорректное значение
IMHO it would be good to add anchordockingdsgn.lpk, sparta_dockedformeditor.lpk and sparta_mdi.lpk packages to the default installation set.
Don't, at this stage, know where the RTL lives ....
My system is Debian Linux and I'm currently using 1.6.4 which I installed using the debs from the previous release. Should I remove these packages before installing the new debs?You should uninstall the old version to be on the safe side. I am not sure how the Debian package system does the update.
I HAD 1.8 installed, it compiles slowly, then the compiled basic default window takes forever to show up after being compiled. I do not remember Lazarus being that slow.Usually just first time use. After that you should not notice any difference.
I HAD 1.8 installed, it compiles slowly, then the compiled basic default window takes forever to show up after being compiled. I do not remember Lazarus being that slow.Usually just first time use. After that you should not notice any difference.
... , the "slowness" is mostly just me not remembering How Lazarus does that compiling speed.Most basic used classes/components are build/compiled on the first compilation run, sometimes resulting in an very annoying slowness (same happens when you switch widgetset/target and recompile your project for the first time). Once compiled things go must faster. Also the OS usually caches things better the longer you use lazarus.
I can not run this version 1.8 on Linux, and I have the same problem with Mageia 64 bit (installed with RPM packages) and with Mint 64 bit (DEB packages): link editing is not possible ( I checked the platform options, etc.).
If I install FPC 3.0.4 alone, downloaded on freepascal.org, compiling and linking is done worry free.
If I add the downloaded Lazarus 1.8.0 package to SourceForge, then the expected version of FPC is not the right one (it wants 3.0.4 release 1). OK, let's give him the right version. I uninstall version 3.0.4.
I'm now installing version 3.0.4.1 alone, available with Lazarus 1.8: link editing does not work - with a very terse error message 'Error while linking'. Lazarus installs without problems later, but hey without being able to edit the links, I'm stuck.
... , the "slowness" is mostly just me not remembering How Lazarus does that compiling speed.Most basic used classes/components are build/compiled on the first compilation run, sometimes resulting in an very annoying slowness (same happens when you switch widgetset/target and recompile your project for the first time). Once compiled things go must faster. Also the OS usually caches things better the longer you use lazarus.
Unfortunately I have no experience with the other issue...
BeanzMaster, forget the packages. After installing FPC, checkout Lazarus sources from SVN fixes_1_8 branch and build with "make".
My experience also is that installing packages outside the distro's repository often breaks something.
Either bypass the package system or use a rolling distro which has recent versions of everything.
I can recommend Manjaro from my experience.
sudo apt-get purge fpc
sudo apt-get purge lazarus
sudo apt-get remove /etc/fpc.cfg // this one must be done by hand because the package manager forgot about it...
sudo apt-get autoremove
Then install....
You may ave to re-install some dependencies, or skip autoremove.
Never was so much owed by so many to so few. :)https://www.youtube.com/watch?v=Y0t-RqjMH-A
Thx.
... but I see that UpperCase does not work the same as UTF8UpperCase.Please open a new thread for this.
... but I see that UpperCase does not work the same as UTF8UpperCase.Please open a new thread for this.
It is not related to Lazarus 1.8 release.
I only found one small thing in FPC (don't know where to report it): the variable FPC_FULLVERSION is set to 30000 but it should be 30400.It isn't set to 30000 (I think). I think it is set to 030004.
Just always test: here's a utility for that:I only found one small thing in FPC (don't know where to report it): the variable FPC_FULLVERSION is set to 30000 but it should be 30400.It isn't set to 30000 (I think). I think it is set to 030004.
2.6.1 was 020601 so 3.0.4 would be 03 00 04 (which is 030004).
(take 00 "format" for each number)
TMemo.SelText problem persists, two latest patches were no applied.A bug report should be reopened if the bug still persists. Comments in a resolved issue are typically not followed.
https://bugs.freepascal.org/view.php?id=32583
@antekgla
Can you supply a small example that demonstrates the issue? I cannot reproduce the bug, TPageControl works fine both on Lazarus_1.8 and Lazarus_trunk. Download the attached project then press: Alt + P, Alt + F, etc...
@antekglaI really don't like debug third party applications/components. However, it looks like you have some relevant code in PageInfo(TPageControl) OnChange event. The big difference between 1.6 and 1.8, is that in case of 1.6 the OnChange event is automatically called when you programmatically change ActivePageIndex. To do the same in 1.8 just set nboDoChangeOnSetIndex to true in the form OnCreate event, with ifdef to avoid code break.
I dont know how reproduce this issue in a new project.
You can compile TransGUI is not a complicated program. I am a newbie in Lazarus and I can compile without problem.
Only need install a component (included) in the sources (TVarGRid).
I really don't like debug third party applications/components. However, it looks like you have some relevant code in PageInfo(TPageControl) OnChange event. The big difference between 1.6 and 1.8, is that in case of 1.6 the OnChange event is automatically called when you programmatically change ActivePageIndex. To do the same in 1.8 just set nboDoChangeOnSetIndex to true in the form OnCreate event, with ifdef to avoid code break.
uses ...LCLVersion; procedure TMainForm.FormCreate(Sender: TObject); begin //... {$IF LCL_FULLVERSION >= 1080000} PageInfo.Options := PageInfo.Options + [nboDoChangeOnSetIndex] {$ENDIF} end;
This will most likely fix the issue.
Hi i have a problem as shown above,can someone help me?