Oh - it's quite easy to become confused while searching for a mistake and trying to narrow down it by adding some additional logs
which only show the (non unique) numbers and not the (more or less - at least for insiders ;)) self-explanatory identifiers.

And if you're looking during search for ...

Hi boskid,

thank you for the really quick answer. Ok - that looks like some apparently desired redundancy, but shouldn't this be reflected in the json-docu at https://lua-api.factorio.com/stable/runtime-api.json, too? Otherwise it's a little bit misleading

I've just stumbled upon a strange behavior concerning the values of defines.wire_connector_id.*

When using these defines I had some strange phenomenons. For digging a little bit deeper I wrote this tiny "mod"


for _, f in pairs(defines.wire_connector_id) do
log(f)
end


and expected to see the ...

Nowadays the page with the documentation is located here: https://lua-api.factorio.com/latest/typ ... gType.html

Thx for your efforts and I am excited about the solution

Hmm, can you try setting it after creation?

local sp = container.add {
type = "scroll-pane",
style = "rldman_small_slot_table_scroll_pane",
name = "scrollpane"
}
sp.horizontal_scroll_policy = "dont-show-but-allow-scrolling"


Of course :D

Code now is

local sp = container.add {
type ...

Oh yeah, you're right - that is wrong

Unfortunately there is no change in behavior after correcting this (I've checked whether the policy is now set correctly by logging the content of the field)

Hi Klonan,

thx for your quick response.

This is the relevant part of the code, where the scroll pane sp is created:


function testtab.update(refs, data)
local container = refs.testtab_tab

-- ugly - clear all children and create new ones
container.clear()

local sp = container.add {
type ...

Is it possible to have a scroll pane without scrollbars which is still scrollable (with mouse wheel)?

I've already tried the *_scroll_policies with "dont-show-but-allow-scrolling", but unfortunatelly scrollbars are still shown and I can't see any difference in behaviour to "auto".

Thx in advance

OP, did you finish connecting the green wire to a target?
Because in that setup (a belt right next to a combinator) it may look like the wire is connecting to the combinator, but it's indeed connecting to the belt.
Connecting a wire to the combinator looks a little bit differently:
GreenWireOnBelt ...

Tried to connect a belt with green wire, instead of the chosen transportation belt the adjacent combinator was connected.

The behavior is easy reproducible:
choose green wire
try to connect belt and click it
instead of the belt the combinator is connected

Both arithmetic and decider ...