El 15/11/16 a les 19:12, Luca Olivetti via Lazarus ha escrit:
El 15/11/16 a les 18:46, Luca Olivetti via Lazarus ha escrit:
El 15/11/16 a les 17:48, Luca Olivetti via Lazarus ha escrit:
El 15/11/16 a les 15:42, Mattias Gaertner via Lazarus ha escrit:
The Lazarus team is glad to announce the release of Lazarus 1.6.2. This
is a bugfix release.

This release was built with FPC 3.0.0.

Is it supposed to work even with 2.6.4?
I have to investigate why but a TDBLookupComboBox doesn't work anymore
(with fpc 2.64/win32).

I tried under linux 64 bits/gtk, with fpc 3.0.0 the TDbLookupComboBox
works, with 2.6.4 it doesn't.
The symptom is the same: the combobox has the correct number of options
but all of them are blank.
If it's supposed to work with 2.6.4 I can file a bug report.

transplanting lcl/include/dblookup.inc from lazarus 1.4 to 1.6 "fixes"
the issue (which is funny, since the new one apparently has some ifdefs
that only modify the behavior with fpc < 3.0.0).

OK, I'm using a TSdfDataset, maybe it has the same bug as TMemDataset as mentioned in dblookup.inc (but then I don't understand why it worked with lazarus 1.4).
FWIF, this appears to fix it:

===================================================================
--- lcl/include/dblookup.inc    (revision 53370)
+++ lcl/include/dblookup.inc    (working copy)
@@ -274,7 +274,7 @@
   Bookmark := ListLinkDataSet.GetBookmark;
//in fpc 2.6.4, TMemDataset does not supports BlockRead. Issues 26356, 27959
   {$IF FPC_FULLVERSION < 30000}
-  DatasetSupportsBlockRead := not IsClass(ListLinkDataSet, 'TMemDataset');
+ DatasetSupportsBlockRead := not IsClass(ListLinkDataSet, 'TMemDataset') and not IsClass(ListLinkDataSet, 'TFixedFormatDataSet');
   if DatasetSupportsBlockRead then
     ListLinkDataSet.BlockReadSize := 1
   else

--
Luca Olivetti
Wetron Automation Technology http://www.wetron.es/
Tel. +34 93 5883004 (Ext.3010)  Fax +34 93 5883007
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus-ide.org/listinfo/lazarus

Reply via email to