Some trouble to get what I expect with UI #126
Comments
|
First thing I noticed is that the big section of empty space is coming from this: The first parameter of Has a much better result. But I am still trying to figure out where the empty space in the "stage" section it coming from, this looks more like a bug. |
untoldwind
added
bug
|
With it should now look like this in 0.5.2.8
Additionally I added an you can use |
|
Additional note: The problem seems to be that the initial layout still calculates with the larger font size if it is tweaked later. I am not entirely sure how to fix this behavior yet |
|
Lil bit of rework on my side, and this is what I get : I'm happy !
Hitten by the truck of realisation. With better understanding, it's obvious.
Nice ! Thank you !
I see. Now, It's my turn to find a trickery to gather the initial stages' record array AND initialize fontsize.
The update loop use this two fact to shorten the stage section when it's needed. Note : const shipName = shipField
.add_label("", Align.Start)
.bind(sName, "name".pad_right(pRight) + " : {0:" + pLeft.to_string() + "}")where the size could be actualy initialized right with already known number of characters, but as Navigation and Orbital don't use any Additional question : Many thanks, I'll keep you in touch ^^ Edit : formating |
|
Just a question, which may lead to an idea. Frame 1 (game in pause to catch it) After first update and label trick, window have upscale (without label trick, it don't) After decouple a stage, container update as intended (with label trick on the labels of the stage 3), but not the window : How did you manage to automaticly upscale the window after initialization when it's to small for it's containers ? Edit : typo, as often... |
|
Yes, the window starts out with a vertical container/layout (I figured this to be the most common use-case), but I guess it should be possible to make this configurable in the The issue with the empty vertical space boils down to a race-condition. The window actually opens the moment I'll add some helper functions to resize/compact/recenter a window via script, which should resolve the issue. |
|
Since I did some pretty heavy (long overdue) refactoring as well, I created a pre-release for this: In you example, adding a : (see: https://kontrolsystem2.readthedocs.io/en/prerelease/reference/ksp/ui.html#center) after all components have been added should now do the trick. Additionally I added support for removal of components from the window. So something like this should now work as well: |
|
You bring Chrismas everyday :) |
|
Look at what you have done ! The only drawback currently is I don't understand why sometimes label's button is inverted with datas. (As pictured : button suggest to switch to datas corresponding 'to full-ignited full-throttle at this pressure' condition when it obviously already show them. It should show 'Switch to Current', corresponding to real time datas, as 0.0N of thrust as intended for offline engines. But Eh... When I click it, data switch, good enought at the time. I'll investigate later, and if I get a deadend, I'll bother you with thoses stuff. Edit: typo |
|
I did a very simple test, which worked fine: |
|
Hum... I wrote something very close. Or if I didn't, it's a misprint. The only major difference I'm able to notice, is I used the |
|
Good point, I tried out with a more functional approach: ... which seems to work just the same |
|
This issue is stale because it has been open for 60 days with no activity. |
|
This issue was closed because it has been inactive for 14 days since being marked as stale. |
version 0.5.2.7 (Ckan)
assumed tag : question
Hi !
I want to do a screen who synthetize some real time datas about my flight, usefull for information or debug.
What I think i have understood about
ksp::uimodule :Align) seems match with the position the container will have inside his parent container.Startwill be up,Centerwill be middle height,Endwill be down. If their is several children with Align.Start arguments, they will be added in the order where they were processed. (It can be a different order than the one you write them : example : records are processed alphabeticaly)Stretchwill stretch the width of the vertical container to the width of it's parent containerAlign) seems match with the position the container will have inside his parent container.Startwill be left,Centerwill be middle width,Endwill be right. If their is several children with Align.Start arguments, they will be added in the order where they were processed.Stretchwill stretch the height of the horizontal container to the height of it's parent containerI'm probably wrong somewhere since I'm not able to get what I expect.
This is what I expect to get (at first):
And how I think it should be built :
Here the work in progress code:
ui::monitor.to2
I don't think it's revelant to give details about how
shipandstagesare built to understand howMonitorshould work. For the most, it's custom methods to thrust, isp, twr, deltaV etc which are able to give me reliable data even when I should't get thoses, and some shorteners for usefull datas : (deltaV for separatrons, expected thrust even when the engine is off, thoses kind of things)And now, with this nice bunch of code, this is what I get :
An oversized window, panels shifted and streched in ways I'm not able to understand, even outer the window, labels greater than their parent panels, in short, a mess.
So I have undoubtly done something wrong, but here the trick : I don't have a clue what about.
At least, datas are corrects ! :)
Edit : still not fluent in english
The text was updated successfully, but these errors were encountered: