Lazarus 1.2.2 Release

[motaz]

Does the Issue persist? Can you resize horizontal and vertical independent form each other?

yes, the problem still there, I can resize only when I manually modified Width and Height properties in object inspector.
I've tried independent and both resize, both fails. While holding mouse button I can see the resize pointer, when I release it, it returns to it's original size.

[ahmadian]

Hi all
Download link of Lazarus 64bit is not true in below page:
http://www.lazarus.freepascal.org/index.php?page=downloads

It links people to 32bit version. so the correct link seems to be below:
http://citylan.dl.sourceforge.net/project/lazarus/Lazarus%20Windows%2064%20bits/Lazarus%201.2.2/lazarus-1.2.2-fpc-2.6.4-win64.exe

[BigChimp]

Ahmadian: this is intentional. See the release announcement in the first post for the reason why people are recommended to use the 32 bit version on 64 bit windows.

[o8o8]

 

感謝你們的努力 !

[Nyerguds]

BigChimp: The Win64 version thing is pretty confusing... you should indicate that on the downloads page, or just make it one "32/64 bit Windows" link.

The only thing your "intentional" wrong link did for me was making me look into the sourceforge files to find the real 64 bit version. And judging from Ahmadian's post, that would be the standard reaction of most people who would click the Win64 link and notice the filename.

[rhapdog]

The only thing your "intentional" wrong link did for me was making me look into the sourceforge files to find the real 64 bit version. And judging from Ahmadian's post, that would be the standard reaction of most people who would click the Win64 link and notice the filename.

I'm afraid that's very true. I would have gone there looking for it as well, had I not just read about this here first. The links should be changed to reflect what they point to, and a notice to explain why.

I think I'll just stick with the 32-bit and cross-compile until the kinks are worked out. I don't like it, but how often in life do we get everything exactly the way we want it? I'm supposed to be a multi-trillionaire by now according to what I was wanting when I was in High School. But at least I never go hungry. 

Looking forward to the real 64-bit support that has been fixed and/or is being worked on. Can't wait to test drive that one.

[BigChimp]

BigChimp: The Win64 version thing is pretty confusing... you should indicate that on the downloads page, or just make it one "32/64 bit Windows" link.

It's mentioned in the release notes. It's mentioned on the wiki. It's even mentioned in the readme in the files section of the win 32 bit download and the win 64 bit download on sourceforge.

If people don't read things, well... it's no wonder they get confused.

@rhapdog: FPC trunk (2.7.1 currently) and Lazarus trunk work very well together; you can have a separate setup (with different --primary-config-dir) completely apart from your regular lazarus install; use e.g. subversion/svn to get it or use fpcup (which uses svn behind the scenes. Disclaimer: I'm one of the fpcup authors).
That said, I really wonder what you're missing with the 32 bit IDE... it's not as if Laz memory demands require a 64 bit IDE and you can cross compile without worries... maybe it's just me. (Personnally, I'm on Laz trunk+FPC trunk x86 for that reason).

[photor]

BigChimp: The Win64 version thing is pretty confusing... you should indicate that on the downloads page, or just make it one "32/64 bit Windows" link.

It's mentioned in the release notes. It's mentioned on the wiki. It's even mentioned in the readme in the files section of the win 32 bit download and the win 64 bit download on sourceforge.

If people don't read things, well... it's no wonder they get confused.

@rhapdog: FPC trunk (2.7.1 currently) and Lazarus trunk work very well together; you can have a separate setup (with different --primary-config-dir) completely apart from your regular lazarus install; use e.g. subversion/svn to get it or use fpcup (which uses svn behind the scenes. Disclaimer: I'm one of the fpcup authors).
That said, I really wonder what you're missing with the 32 bit IDE... it's not as if Laz memory demands require a 64 bit IDE and you can cross compile without worries... maybe it's just me. (Personnally, I'm on Laz trunk+FPC trunk x86 for that reason).

Why free pascal supress the "extended" floating point type on win64 platform? Then how to achieve high precision floating point operation on win64 platform?

[Rails]

Why free pascal supress the "extended" floating point type on win64 platform? Then how to achieve high precision floating point operation on win64 platform?

This Embarcadero document has an explanation. As I read it, it's Win64 itself that is the issue.

"In Win64, the precision of floating-point computations was reduced from extended (10-byte values) to double (8-byte values)."

http://docwiki.embarcadero.com/RADStudio/XE3/en/W1066_Lost_Extended_floating_point_precision._Reduced_to_Double_(Delphi)

[Nyerguds]

BigChimp: The Win64 version thing is pretty confusing... you should indicate that on the downloads page, or just make it one "32/64 bit Windows" link.

It's mentioned in the release notes. It's mentioned on the wiki. It's even mentioned in the readme in the files section of the win 32 bit download and the win 64 bit download on sourceforge.

If people don't read things, well... it's no wonder they get confused.

Honestly? No one who just downloads the IDE to start programming on it will read those, no. People who update their install, sure, they tend to skim over the release notes to see what's changed and updated. But for people who don't already have it installed, it's utterly useless to go dig through a bunch of stuff like that just on the off chance there's something odd somewhere. IDEs are generally pretty intuitive, unless they're doing something wrong.

Heck. Go to the main page. What do you see? A large "download" button, straight to the installer. Not a single step in between. And you expect people to read release notes?

[BigChimp]

Well,

1. those people get a perfectly suitable installer for their Windows 64 system.
2. yes, I expect them to read release notes. Obviously you don't. Let's agree to disagree.... or
3. what specific, concrete suggestion do you have to improve things?

[ChrisF]

Why free pascal supress the "extended" floating point type on win64 platform? Then how to achieve high precision floating point operation on win64 platform?

I guess it's because x87 is considered deprecated by Intel: SIMD/SSE2 have to be used instead.

And while x87 used 80 bits registers, most compilers use generally only 64 bits SIMD registers  for their double precision floating-point instructions.

Edit: I've missed that FPC 2.7.1 will get the support of AVX SIMD instructions (128 and 256 bits registers). I guess that extended floating point instructions will be reintroduced at this step.
.

[Nyerguds]

3. what specific, concrete suggestion do you have to improve things?

Since there's only one real Windows download link on the downloads page... rather than the unintuitive copy, it's more logical to either remove the 64 bit Windows link, or to give the real 64 bit link, but with the warning and the link to the wiki added right next to it.

Either of these will indicate to the user that use of the 64 bit version is not recommended.

[BigChimp]

I don't think think SourceForge supports the latter.

The former sounds doable, yes. I wonder what the Laz devs involved with the installation think about this... If this doesn't get a response (I suspect Martinfr who usually responds to these kinds of questions is extremely busy at the moment), you could raise an item in the bugtracker so it gets seen, tracked (and not forgotten).

[Martin_fr]

I added a further warning at sourceforge. This is in form of a file, where the file name contains the warning.

So now, if you open the folder at sourceforge, it will be right there. You have to read file names anyway to find which file to download.