Increase the Height of the LanguageSource Inspecto

More
5 years 3 months ago #133 by aholla
Hi, I have just started using l2 and so far so good. I did have problems getting it to parse my csv file correctly, it seems I have to label my colums correctly eg Terms, Type, Description, not "Keys" as shown in the example.

Anyway, I would really like to be able to expand the inspector widget so that it takes up the how inspector rather than 500px or so. Where is the height specified?

Thanks!

Please Log in or Create an account to join the conversation.

More
5 years 3 months ago #139 by Frank
Hi,
The plugins requires specific columns names in order to recognize that the spreadsheet has the right format. So normally, its a better idea, to add a few empty languages to the LanguageSource, and then export the spreadsheet so that it generates the right format.
Once you have the right spreadsheet you are safe to add new terms and they will be imported to the i2 source.

The list of terms in the inspector is set to 300px at the moment.
Initially it was to expand to cover all the screen height, but when more than one component was in the same object than the source it was hard to edit the other components.

The line that sets the height of the list is on LocalizationEditor_Terms.cs line 34
void OnGUI_KeysList(bool AllowExpandKey = true, float Height = 300.0f, bool ShowTools=true)

Are you :-) Give I2L 5 stars!
Are you :-( Please lets us know how to improve it!
To get the betas as soon as they are ready, check this out
The following user(s) said Thank You: aholla

Please Log in or Create an account to join the conversation.

More
5 years 3 months ago #145 by aholla
Cool I found it. I also took the liberty of adding a slider that dynamically changes the height of the panel. I wonder if anyone else might find this useful until a better solution is available anyway.

(The height in the "LocaliseEditor_Terms" is set to a static float which is set via the inspector in "Language source Inspector")

Thanks.
Attachments:

Please Log in or Create an account to join the conversation.

Time to create page: 0.311 seconds
Template by JoomlaShine