Hybrid Overhead Camera (v4)

[Regret]

eat shit

[Jazcash]

Pix or it doesn't exist.

[Regret]

Pix or it doesn't exist.

What on earth you want pix of? It's a camera.

[Caydr]

Sounds like a hoax to me.

[SinbadEV]

Pix or it doesn't exist.

What on earth you want pix of? It's a camera.

Video?

[luckywaldo7]

Imaging being able to use the overhead camera at that angle and you will understand this widget.


Feature request: move camera with arrow keys (probably will become my default camera mode then).

[Jazcash]

Imaging being able to use the overhead camera at that angle and you will understand this widget.

Ctrl+Mousewheel?

[imbaczek]

TA overhead can't rotate around y axis.

[Regret]

Updated, included arrow movement and lots of tweaks/fixes.

[Regret]

Updated, included a fix for compatibility with smooth camera. (thx BrainDamage)

Also now middle click / J movement is just like in normal overhead cam, even with crosshair.

[Regret]

Update, fixes and tweaks, now properly supports F3.

[Gota]

Can you add an otion to make the camera only zomm out till u see the entire map and not more.

[manolo_]

why did u deleted the whole widget and reuppt it, the older versions are a feature not a bug

[Regret]

why did u deleted the whole widget and reuppt it, the older versions are a feature not a bug

I don't consider old bugged versions as features.

Can you add an otion to make the camera only zomm out till u see the entire map and not more.

Press TAB.

[very_bad_soldier]

why did u deleted the whole widget and reuppt it, the older versions are a feature not a bug

I don't consider old bugged versions as features.

Aha. So, what exactly is wrong in offering an archive of old versions like every reasonable open-source project (http://springrts.com/dl/) does?

[Regret]

Aha. So, what exactly is wrong in offering an archive of old versions like every reasonable open-source project (http://springrts.com/dl/) does?

Nothing, just don't expect it for things for which it is useless.

[mongus]

on this subject i consider the lua-spring comunity to be taking a mistaken path.

what happens, is lua scripts are getting named with the same name, every version, effectivley overwritting old versions scripts.
This behaviour is not needed, as naming a gadget luacrap_v1.lua and the next version luacrap_v2.lua, does not change its enable/disable state in the lua selector screen.

Im sure there is lots of learning material for programmers related to this stuff (naming conventions and versioning).

Historical archiving is lost this way.
I see some reasons for historical archive, for example learning from mistakes, reusing old code, having a wide, open source repository of lua code, etc.

Isnt ca downloader endorsing this (mistaken) naming convention?
i strongly suggest this ppl to do something about it, for example, ca downloader already deletes older versions of the ca mod, why not to do the same with widgets?

But this and 2 previous posts are way offtopic and could have their own thread... well.

[Regret]

on this subject i consider the lua-spring comunity to be taking a mistaken path.

what happens, is lua scripts are getting named with the same name, every version, effectivley overwritting old versions scripts.
This behaviour is not needed, as naming a gadget luacrap_v1.lua and the next version luacrap_v2.lua, does not change its enable/disable state in the lua selector screen.

Im sure there is lots of learning material for programmers related to this stuff (naming conventions and versioning).

Historical archiving is lost this way.
I see some reasons for historical archive, for example learning from mistakes, reusing old code, having a wide, open source repository of lua code, etc.

Isnt ca downloader endorsing this (mistaken) naming convention?
i strongly suggest this ppl to do something about it, for example, ca downloader already deletes older versions of the ca mod, why not to do the same with widgets?

But this and 2 precious posts are way oftopic and could have their own thread... well.

The reason I name them alike is so you don't have 2 versions of same widget on at the same time. I don't care about your needs to keep old outdated scripts that are bugged.

[very_bad_soldier]

what happens, is lua scripts are getting named with the same name, every version, effectivley overwritting old versions scripts.

Im sure there is lots of learning material for programmers related to this stuff (naming conventions and versioning).

Historical archiving is lost this way.
I see some reasons for historical archive, for example learning from mistakes, reusing old code, having a wide, open source repository of lua code, etc.

There is a historical archive. You can download every single version of a widget (besides the ones deleted by regret ) in SpringDownloader.
I dont think your spring widget folder is the right place for a historical archive though.

I don't care about your needs to keep old outdated scripts that are bugged.

A newer version doesnt automatically mean less bugs.

Sorry for being offtopic Regret. Just say if I should shut up.

[Regret]

A newer version doesnt automatically mean less bugs.

Sorry for being offtopic Regret. Just say if I should shut up.

With my widget it means less bugs, that's why I don't keep old versions.

And I don't mind the free bumps :p