Page 1 of 1

[0.15.2] [Twinsen] Inserter Stack Size Option Inconsistency (minor)

Posted: Wed Apr 26, 2017 8:39 pm
by Deadly-Bagel
When you connect an Inserter to the circuit network you get the option of setting a static stack size or setting one from the circuit network. The two options are tied so when you select to get stack size from circuit network, it force enables the static stack size and you can't disable it.

There is however some odd behaviour to this. If you disable then re-enable "Set stack size" you can toggle "Override stack size". Also if you disable Set Stack Size then re-enable it, Override Stack Size might not even get reticked at all. This is purely a visual bug, it does not affect the behaviour of the Inserter and if the GUI is closed and re-opened the Override stack size option is re-enabled if Set stack size is enabled.

Disable and re-enable this option:
20170426213432_1.jpg
20170426213432_1.jpg (89.2 KiB) Viewed 1523 times
Disable "Override stack size"
20170426213437_1.jpg
20170426213437_1.jpg (89.25 KiB) Viewed 1523 times

Re: [0.15.2] Inserter Stack Size Option Inconsistency (minor)

Posted: Sun Apr 30, 2017 8:00 am
by LegendaryXeltan
1. This still happens in 0.15.4.

2. Similar bug
Opening the inserter GUI with unchecked Override stack size (OSS) and Set stack size (SSS).
Enable just OSS by left click and SSS keeps unchecked. This stays also after closing und reopening the inserter GUI. Also the stack size override works.

If OSS is enabled, SSS does nothing. Enabling and disabling SSS doesnt effect stack size override and it doesnt untick the OSS checkbox like it should.
Image

3. Similar bug
The stack size can only be set if OSS is enabled and SSS is disabled. If you toggle SSS and therefore the OSS and SSS checkboxes get ticked, the stack size works, but cant be changed.

Re: [0.15.2] [Twinsen] Inserter Stack Size Option Inconsistency (minor)

Posted: Fri May 19, 2017 2:34 pm
by kovarex
Redirected to twinsen.

Re: [0.15.2] [Twinsen] Inserter Stack Size Option Inconsistency (minor)

Posted: Wed May 31, 2017 12:50 pm
by Twinsen
This was fixed some time ago but I forgot to move this bug.
Everything should be ok.