Hi!
Is the BGRA Version Number somewhere stored inside the units?
I didn't find anything.
If not, this is a wish for future releases:
Put the Version Number somewhere into BGRA.
Thanx, Winni
Hi!
Is the BGRA Version Number somewhere stored inside the units?
I didn't find anything.
If not, this is a wish for future releases:
Put the Version Number somewhere into BGRA.
Thanx, Winni
https://github.com/bgrabitmap/bgrabitmap/releases
It's easier to see with open eyes ... :P :)
@dsiders: It's as relevant as the version number in Lazarurs/LCL is and as the version number in fpc is.
What you can try to do is execute a program every new release is added.
That program reads the version number from the package and stores it into a BGRAVersion.pas for example.
As a matter of fact, I did the latest releases like this:
- update package and JSON file with new version (and merge with master branch)
- hope package manager does not read it in the next seconds
- make a release to get the zip file
I wonder if that could be a problem.
cd ..\..
manager update_BGRABitmap.json
archive https://github.com/bgrabitmap/bgrabitmap/archive/v$(Version).zip
cd bgrabitmap
package bgrabitmappack.lpk
package bgrabitmappack4fpgui.lpk
package bgrabitmappack4nogui.lpk
const bgrabitmaptypes.pas BGRABitmapVersion
Though there is a problem as well with doing the JSON afterwards.
When publishing the version on Github, it creates the zip file with the current content of the JSON file. So if the JSON has not been updated yet, then in the zip file to be downloaded the JSON file will not be up-to-date.
Thanks I will try to add to BGRAControls as well.I've added some code to handle both formats. Does it work for you now?
Edit: I try but seems that we have different JSON format, I asked GetMem here
https://forum.lazarus.freepascal.org/index.php/topic,34297.msg319004.html#msg319004
The thing is the zip is done by GitHub when releasing the version, which is done on the master branch, which contains the JSON. So indeed I update the JSON before doing the release. So for a few seconds, the link to the zip file doesn't work.Though there is a problem as well with doing the JSON afterwards.
When publishing the version on Github, it creates the zip file with the current content of the JSON file. So if the JSON has not been updated yet, then in the zip file to be downloaded the JSON file will not be up-to-date.
Then update the JSON before zipping. :)
I'll have to give a look to that releaser: it may save me the time of writing my own if it can be adapted to my needs. I'm geting tired of clumsy, mostly ad-hoc scripts ;)Ok. If you have some improvements, I will be happy to hear about it.
cd ($LogicDir)/lazpaint
project lazpaint.lpi
package lazpaintembeddedpack.lpk
const lazpainttype.pas LazPaintVersion