Don't overwrite code files in update

[Gonan]

Hi Josh,

I recently got Ultra engine, and have been watching your workshop videos.  Im retired now, but still have an interest in programming.

I would like to have a tutorial on how to set out my project file structure so that when I create my project source files they work with yours but would not be impacted by changes to your files as you update ultra engine. One for Lua and one for C++.

I found this was one of my issues with Leadwerks, as I would edit your files, which would later be updated by a patch or new version. The more I put into creating my code the bigger the amount of rework required for each update to the supplied source code.  While its useful for people learning to start this way, It quickly becomes a technical burden for anyone who starts to get productive.  I think this would be a very usefull to put beginners on the right track, and give Ultra engine a better chance of becomming the engine of choice.

I'm so pleased that you are close to releasing Ultra Engine 1.0. and really hope it goes really well for you.

All the Best 

Gonan. 

 

[Josh]

That doesn't sound like a tutorial so much as a suggestion to modify some behavior.

In the options dialog, there is a list of file that should never be updated:

It sounds like this should maybe be expanded to include wildcards and *.lua and *.cpp should be added to the list by default?

[Josh]

This will work in the next build, but you must add *.cpp, *.h and *.lua to the options yourself, since the options are already set in your program settings.

[Thirsty Panther]

The way I worked around this problem was to copy Josh's file and rename it.

For example FPS.Lua became MyFPS.Lua. That way any updates left my code alone.