[1.0.4] KSPAPIExtensions V1.7.5 - Utilities for shared mod use 25 Jun

[Cydonian Monk]

When you do officially release the update, could I ask a favor? Could you check that all of the files for this are in the github repo and up to date? (Including any modified solution files?) I've been trying to tweak and/or rebuild KAE since.... 0.24?.... and as of yet I've never been able to get a clean build of it from either Visual Studio or Mono. (Or is there something bizarre you're doing to build this?)

Thanks.

[NathanKell]

Cydonian Monk: You need VSE (or VS) 2012 or above, it doesn't compile on 2010.

taniwha, thanks so much! As always. And at this point taniwha *is* the author, folks, I just edit the post.

[bac9]

Is the requirement to announce the intent still in effect? I'd like to use the library in my procedural wing mod to solve issues with stock float sliders not allowing proper selection of all possible values.

[taniwha]

bac9: I have no idea.

[bac9]

bac9: I have no idea.

Judging from the post with "certified" modders being last edited in the beginning of September, I would guess no one would mind.

[taniwha]

That's my guess, too.

[Master Tao]

There also haven't been any posts here announcing new mods using it in that time. Any moderator can update it, and at a minimum, I'm subscribed to this thread.

[NathanKell]

It's notionally my job to update the list. If I've missed people, sorry; but since the requirement, as I understand it, was to make swamp_ig's job of maintaining KAE easier, and since taniwha is now maintaining it, it should be fine if he says "don't bother."

[plausse]

Another of my braindead questions..

Is it enough to have one KSPAPIextensions dll somewhere in GameData, or do you need one per mod that uses it?

Thanks...

[taniwha]

plausse: if they're all using the same version, then one is enough, but it's hard to know who's using what, so yeah, you need one per mod. it doesn't take much memory, though.

[plausse]

Thanks taniwha - was just wondering because one of them broke. Or I broke it I think. Updated my version of b9 procedural and suddenly all kspapie tweakables worked at a framerate of circa 5.. Odd. It worked again when I removed said copy, with superficially no ill effects. Maybe next unicorns will die

[gilflo]

Hello

I have a question about KSPAPIextensions: Do I need to put the folder with its plugin in the Gamedata folder as many adds on in the Game data folder have a plugin folder with KSPAPIExtensions.dll ?

Thank's

[NathanKell]

No, unless you are a developer you shouldn't need to use this thread (and this download) for anything.

[gilflo]

Ok thank you, I am not a developer....

[pellinor]

Is there a way to lock the right click menu in place while dragging the slider of a KSPApiExtensions Float-edit field? When TweakScale changes the part size, the menu wanders off with the center of the part, making it difficult to stay on the slider.

Edit: I have taken over the maintenance of TweakScale from Biotronic, so I am also a user of KSPApiExtensions now.

Edited February 22, 2015 by pellinor

[pellinor]

When compiling the source from Github, I get the following problems:

the .csproj (and also the makefile) references two files that are not part of the repo:

* tagged_classes.cs

* Properties\AssemblyInfo.cs

Without them, monodevelop seems to compile fine. However, after compiling TweakScale against the new dll, the Tweakable is missing and the alt-F2 log shows the following (appears 2x per right click on any part with tweakScale module):

[Error]: item prefab for control type 'UI_FloatEdit' not found.

Am I doing something wrong? My plan is to make a variant of the float tweakable that supports variable increments (like 0.625 - 1.25 - 2.5 etc).

[taniwha]

pellinor: they are generated files and thus not in git. Look at the version rule in Makefile.

[pellinor]

Finally got it to work using the makefile. Thanks for the quick answer!

[pellinor]

I finished a working tweakable: https://github.com/pellinor0/KSPAPIExtensions

It takes a list of interval boundaries (n floats for n-1 intervals). A pair of arrows switches the interval, and the slider allows free tweaking inbetween. The slider increment can be given as a single value, or as a list of length n-1, so that each interval can have its own slider steps. If it detects an inconsistent state, or the number of intervals is zero, the slider and buttons are deactivated and it just shows its value.

Would you like to include this into KAE?

Edited February 28, 2015 by pellinor

[pellinor]

Any status on this, taniwha, NathanKell? If you are not interested in the class, would you help me separate it from KAE? I just don't get how this item prefab registration works.

At the moment I have moved TweakScale to the new tweakable and would like to give out a dev version. Which probably is not a good idea as long as it depends on a custom version of KAE.

EDIT: solved. I managed to separate it.

Edited March 7, 2015 by pellinor

[NathanKell]

Sorry, I've been offline for over a week.

[taniwha]

pellinor: and I've been busy with stuff. Please create a pull request (there doesn't seem to be one on github as of 5-10m ago).

[pellinor]

And I've been a bit too impatient to release the next TweakScale version.

At the moment the tweakable is doing its work fine within TweakScale, so there is no need to hurry. Currently I am also working on stuff for Infernal Robotics, which gave me some ideas to improve the tweakable. So I'd prefer to give it a bit more time before integrating.

As I understand, a pull request means that someting is finished and ready to be merged. Or is it also used for "let's discuss about this piece of WIP code" ?

[taniwha]

well, in the end a PR will have stuff that's finished and ready to merge, but it certainly can be used to discuss WIP code as it allows people to look at and discuss the changes.

[pellinor]

Pull request created.

The thing I thought about for IR is two extra buttons tied to +/-infinity. Most likely they would only be used together with a single interval, so that is better done as a separate thing instead of adding it here.

So from my part the tweakable is finished and ready to merge. Code review is always welcome, since C# is not my native programming language.