Rather go to https://github.com/galfar/imaginglib/discussions
Posted by Galfar
- 29 August 2007, 13:11:34Ok, so I will put the new stuff in a comment to ImagingComponents along with some note.
After the new Lazarus release new stuff will be set as compiled code and old will be put in comment
with note (so someone still using older Laz could find what to do to get it working).
After the new Lazarus release new stuff will be set as compiled code and old will be put in comment
with note (so someone still using older Laz could find what to do to get it working).
Posted by aksdb
- 28 August 2007, 02:00:27Hmm, not that I know of. Probably the best way would be to just attach the patch and a note (readme or something) to svn. After Lazarus 0.9.23 is released, it can be merged (I guess there is no reason for downward compatibility then).
On the other hand ... someone who uses the Imaging Lib from svn, probably also uses Lazarus from svn (or at least he has the necessary skills to do so ;)).
On the other hand ... someone who uses the Imaging Lib from svn, probably also uses Lazarus from svn (or at least he has the necessary skills to do so ;)).
Posted by Galfar
- 28 August 2007, 01:31:04Thanks for the patch. I'll update the source in SVN. Do you happen to know if there is a way to detect Lazarus version during compile time? So that it won't break for people using older Lazarus (it would use old RawImage interface).
Posted by aksdb
- 26 August 2007, 22:17:17In the lazarus revision 11861, the RawImage implementation got changed to a more OO approach, breaking the current implementation of the ImagingComponents.
I attached a patch to resolve this.
I attached a patch to resolve this.
SMF spam blocked by CleanTalk