You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having great difficulty installing LZScene into the IDE on Lazarus 3.2.
I've tried everything, Runtime compiles fine but then design time when 'installed' into IDE from package manager as per instructions, after successful rebuild of IDE, kills the IDE on next restart and I get the following Access Violations... Anyone have any ideas what's going on here? I would really like to experiment with this library for an urgent project nearing completion.
And yes I followed the instructions, ensured the paths and forward slashes are all correct in some of the units as per the github branch.
Regards
StuPot1971
The text was updated successfully, but these errors were encountered:
Seems like the LAZLogger cannot capture an exception somewhere, I wondered if there is a weird dependency between the runtime and designtime packages you have to install. One weird thing I noticed is the instructions tell you to first install the runtime library however when you install the design time library it installs the runtime library anyway. Surely therefore you should install the design time library first, then open the loaded package for the runtime library and click use in project?
Hey folks,
I'm having great difficulty installing LZScene into the IDE on Lazarus 3.2.
I've tried everything, Runtime compiles fine but then design time when 'installed' into IDE from package manager as per instructions, after successful rebuild of IDE, kills the IDE on next restart and I get the following Access Violations... Anyone have any ideas what's going on here? I would really like to experiment with this library for an urgent project nearing completion.
And yes I followed the instructions, ensured the paths and forward slashes are all correct in some of the units as per the github branch.
Regards
StuPot1971
The text was updated successfully, but these errors were encountered: