Guppy

So just to be clear bug rapports are only valid if they can be reproduced on a Ubuntu LTS running an Unmodified/Standard theme Unity DE?

What operating system? How did you delete it? (via steam's uninstall or just plain old hitting delete? ) Try opting into beta and see if that solves it

Right-click on Leadwerks in your steam library and chose properties the last tab has a dropdown that lets you opt-in. After this it should update Leadwerks automagically.

Leon if you uninstalled you need to opt back in to beta

That's a myth - dont take my word for it ask icculus. Steam, Chrome, Opera, Cisco Anyconnect, RAR, Aftershot PRO, Corel Draw, Maya You know what those have in common? They are all commerical closed source programs that works on any linux ( aslong as it has the appropriate packages installed ) - why? because they use standard components instead of trying to reinvent the wheel. That way compatibility it outsourced to whom ever maintains the package for that standard component. And that's just the closed source programs, even a lot of opensource programs provides binary packages that just works ( usually a .deb a .rpm and a .tgz - only difference being HOW it's packaged the provided binaries are the exact same ) *facedesk* Linux Mint (apart from LMDE) IS ubuntu - they take the Ubuntu disk installs it and ADDS a new default desktop environment (cinnamon or mate ), then repacks it and releases it as 'Linux Mint'. ( this is why mint releases lags behind the ubuntu ones ) So "my" 10% linux is no different than installing Ubuntu and then adding the Cinnamon packages and making that default for all users, it's not like I'm asking for gentoo or SuSE support.. This was precisely why I asked the question of where the line is being drawn, because if one package means it's no longer supported then something is wrong

So where do you draw the line? Must it be a freshly installed Ubuntu 14.04? Or am I allowed to install other software? What about other desktops? or other themes? Mint-x for instance is also available for Unity I've said it before and I'll say it again discriminating against Ubuntu derivatives makes as much sense as rejecting bugs from windows users who chose Classic over Aero ( or vice versa )

Isn't monodevelop for C# ( completely different thing ) <includedfile> vs "includefile" Are you sure your writing in C++ ?

Any of you guys running Ubuntu 14.04 with a different desktop ( Gnome 3 / KDE / Mate / Cinnamon / XFCE / etc ) and what if any bugs does this cause with the Leadwerks editor? Getting tired of spending more time debugging the editor than creating stuff so I may just return to Ubuntu, I just cannot stand the Unity touchtop.

Look at the scrollbars ( the one clever thing cannonical has done in recent years )

Just tested it - while it does work slightly better you will notice that radiance has no effect on the way leadworks renders control (particularly visible with toolbars). ps: is there no way to edit a theme in ubuntu? I just wanted to change the control theme not the entire DE theme...

actually the standalone/standard/non-steam doesn't get it completly correct as it doesn't draw arrows on the scroll bars but that I can live with if need be, the steam version in its current state is unusable ( checkboxes are invisible for instance )

At first I thougth it was the color scheme that had gone haywire but as it turns out something is broken in the steam edition of LW in regards to rendering GTK control themes. Using Linux Mint 17's default "Minty-x" as you can see all controls are invisible and selecting anything makes it invisible Switching to Adwaita makes everything look like windows 95 (not how it's supposed to look, but alteast you can use it ) Switching to highcontrast actually renderes correctly (looks but ugly tho) This is NOT an issue in the standalone version; Click on the images for larger views

Heads up - uninstalling the app also opts out of beta, so you will need to opt back in

Amusingly the answer you got there is copied straight from this forum; http://www.leadwerks.com/werkspace/topic/9254-mint-16-ubuntu-1310/ (and yes it's a copy of my answer - why else would a person from south-africa use a danish mirror ) Anyway I updated to mint 17 this weekend installed steam and presto - Leadworks (steam edition) works straight out of the box \o/ ( apart for a some selections making the selected item invisible ) So that should bring some hope for usage on other distros - basically if you can run steam it should also run Leadwerks.

wouldn't a multiple choice poll have made more sense here?

adding pthread and X11 to the linker options it finally compiles

This problem affects all linux users, but std. edition can avoid it by not installing into a directory with spaces - with steam how ever we've little choice as it gets installed into "~/.local/share/Steam/SteamApps/common/Leadwerks Game Engine" Anyway fixing that by replacing $(LeadwerksPath) from the -l options with the actual path fixes that but now the problem becomes; /usr/bin/ld: /home/morten/.local/share/Steam/SteamApps/common/Leadwerks Game Engine/Library/Linux/Debug/Leadwerks.a(Thread.o)||undefined reference to symbol 'pthread_create@@GLIBC_2.2.5'| or more concisely: "pthread_create@@GLIBC_2.2.5" (again this problem doesn't occur in std. edition)

/home/morten/.local/share/Steam/SteamApps/common/Leadwerks||No such file or directory| Game||No such file or directory| Engine/Library/Linux/Debug/Leadwerks.a||No such file or directory| /home/morten/.local/share/Steam/SteamApps/common/Leadwerks||No such file or directory| Game||No such file or directory| Engine/Library/Linux/libluajit.a||No such file or directory| ||=== Build finished: 6 errors, 0 warnings (0 minutes, 0 seconds) ===| It's completely new project I just created, just to make sure i also created a c++ project in the stand alone and the compiles just fine. I can't see anything in the projects files to explain it; (compiletest is standard, Cppandluatest is steam) $ diff compiletest/Projects/Linux/compiletest.cbp Cppandluatest/Projects/Linux/Cppandluatest.cbp 5c5 < <Option title="compiletest" /> --- > <Option title="Cppandluatest" /> 10c10 < <Option output="../../compiletest.debug" prefix_auto="0" extension_auto="0" /> --- > <Option output="../../Cppandluatest.debug" prefix_auto="0" extension_auto="0" /> 25,26d24 < <Add library="pthread" /> < <Add library="X11" /> 27a26 > <Add library="../../libsteam_api.so" /> 31c30 < <Option output="../../compiletest" prefix_auto="0" extension_auto="0" /> --- > <Option output="../../Cppandluatest" prefix_auto="0" extension_auto="0" /> 45,46d43 < <Add library="pthread" /> < <Add library="X11" /> 47a45 > <Add library="../../libsteam_api.so" /> 51c49 < <Variable name="LeadwerksPath" value='"/home/morten/Leadwerks"' /> --- > <Variable name="LeadwerksPath" value='"/home/morten/.local/share/Steam/SteamApps/common/Leadwerks Game Engine"' /> 64a63 > <Add option="-D__STEAM__" />

Randomly stumbled across a batch renamer for blender http://adaptivesamples.com/2013/09/07/batch-renamer/ and remebered this thread Here is a test blend file; https://drive.google.com/file/d/0B7B0hlkpWcYWcWl3ajNHbjdQb3M/edit?usp=sharing Layer 1 has the unbroken object Layer 2 has the broken object ( made a lot of space between to make sure the physics engine doesn't stick them together ) Layer 3 has the collision shapes ( renamed duplicate of layer 2 ) It occurs to me that the the shards and collision shapes must somehow be associated ( child ? ) and each shard should have a mass Can that be done in blender or does it have to be done in LE ?

Not very cross platform and Notting you cant do with raw wapi32 ( GetActiveWindow(); )

Unless the editor is written in some weird language that does not have GTK/QT wrappers, it would actually be a fairly minor change - only the view code changes the model & control layers would remain largely untouched by it. It shouldn't take a year to write that, having to learn GTK on top of rewriting the view layer might, hence I think it should be outsourced to somebody with experience. It's an annoying extra cost, but honestly the current UI ( under linux atleast - I've yet to try it on windows ) feel a bit like trying to do calligraphy with both hands tied behind your back and with somebody randomly coming by to give you a shove.

A very big one - and properly one that needs to be outsourced; Rewrite the editor using standard elements from a stable crossplatform ui toolkit (GTK,Qt or wxWidgets ), this will get rid of many bugs and fustrations ( oh yeah that particular scroll pane cannot be mouse scrolled, scene tab will sometime stop drawing and just display the last tab, etc, etc, etc ) Many of those toolkits comes with a visual designer - GTK for instance has glade/gtkbuilder which abstracts the design down to an xml file, this file can then be edited independently of the functionality which in my book is pure win. With the rewrite there really needs to be support for custom plugins and widgets (w. the glade approach you could even make custom panels ), as well as support for scripting editor actions in lua. Oh and do consider using scintilla for the editor, no point in reinventing the wheel when a perfectly round one already exists and is ready to use.

http://luatut.com/crash_course.html Very handy as you can test stuff without leaving the website thanks to the inline console ( hit ESC ) Once your down with that it's time to hit the docs http://www.leadwerks.com/werkspace/page/documentation Because honestly you have to know at least some lua in order to create something at least vaguely interesting

From what little I remember of german it would seem that you forgot to inform your linker where it can find the library files

That solved it yeah, thanks