A additional remark:
Apparently different installed packages cannot have the same library name in them. When choosing such library in one package it becomes checked in all packages in the mP IDE.
Is this indeed a restriction?
Thanks in advance.
Some issues in PM v2.00
Re: Some issues in PM v2.00
Kind regards, Dany.
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)
Re: Some issues in PM v2.00
This is probably IDE problem, nothing related to the Package manager.
It is on the bug list and in future releases will be resolved.
Thanks for pushing the issue.
It is on the bug list and in future releases will be resolved.
Thanks for pushing the issue.
Re: Some issues in PM v2.00
Indeed, most probably. The mP IDE does no know from which package a library comes.zristic wrote:This is probably IDE problem, nothing related to the Package manager.
Thanks. This issue could be a problem if a users wants to use 2 packages (e.g. from different providers in LibStock) with an equal named (aliased) library in them.zristic wrote:It is on the bug list and in future releases will be resolved..
Kind regards, Dany.
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)
Re: Some issues in PM v2.00
Everything is ok but the crashing thing is unusual.Dany wrote:Here 2 screenshots about PM problems:
1: Refusal to install a package (all libraries in it were allowed for P18... processors) :
mP was not started up at that moment. The package was "saved" in the PM before the install attempt.
2. Crash when trying to close the PM after above refusal
After restarting the PM I could install the package that was refused first.