Hi. As I work out some limitations in the default code and add those to my personal editor, I have to wonder how these fixes might propagate into a released version of Quest? (ie light sources in an inventory do not light up a room, that seems like an obvious oversight that should make it to release)
Do others have to wait for the next version to reap the benefits? (other than updating their own copy of Quest)
Seems like there should be two kinds of updates: Game Engine (C#/java) improvements and ASLX file improvements. The later could be updated and made public much more often than the former.
I'm stil new here so forgive my possible ignoramity.
thanks

Quest is opensource so everybody could add fixes, for lightsources I will do this. Other user must wait for the next version or subversion, if it is a serious problem. I don't think Alex will change the release process. It would be difficult to coordinate single file distributations.
But you could check the nightly builds, if a new version is available http://quest.codeplex.com/releases/view/99971

Actually I do think it would be a good idea to think about how to update libraries more regularly.

It would be good to have a centralised way of distributing updates not just for the Core libraries but for other user-contributed libraries too.

Something like a package manager, like Nuget in Visual Studio.

Probably not any time soon though unless someone wants to volunteer to design and/or code this