Recent

Author Topic: Rearrangement of FPSpreadsheet sources  (Read 2505 times)

wp

  • Hero Member
  • *****
  • Posts: 11916
Rearrangement of FPSpreadsheet sources
« on: October 22, 2016, 11:54:19 pm »
In order to resolve some compilation issues the source files of FPSpreadsheet were rearranged such that the sources of the three packages are separated. Now there's a folder "source" which contains the lpk files and these three subfolders:
  • "common" for the basic fpspreadsheet stuff needed by package laz_fpspreadsheet.lpk
  • "visual" for the visual components (laz_fpspreadsheet_visual.lpk)
  • "export" for the export component (laz_fpspreadsheetexport_visual.lpk).
Projects which do not follow the recommended way of adding the fpspreadsheet packages as project requirements, but set a search path to the fpspreadsheet units, must adapt this search path to the new locations.

In this context it was also necessary to integrate two units into other units:
  • fpsNumFormat.pas contains now also the code of fpsNumFormatParser
  • fpsReaderWrite.pas contains also the code of fpsRegFileFormats
Although these units will be rarely "used" in projects I should mention that any "uses fpsNumFormatParser" and "uses fpsRegFileformats" will have to be replaced by "uses fpsNumFormat" and "uses fpsReaderWriter", respectively.

totya

  • Hero Member
  • *****
  • Posts: 720
Re: Rearrangement of FPSpreadsheet sources
« Reply #1 on: October 23, 2016, 12:57:54 am »
Hi!

Thanks for this information!

I have only one "fpsRegFileformats" in uses line, I changed to "fpsReaderWriter" (but the compile has been success without it).

 

TinyPortal © 2005-2018