epam / epam/Indigo

`setOption` render options are invalid until IndigoRenderer is created.

Open
#1,909 1 comment 0 reactions 0 assignees View on GitHub
User`s Feedback
Dominant language
C++
Stars
406
Forks
134
Avg merge
2d 11h
Merged PRs (30d)
24

Description

Rendering options such as "render-output-format" are not considered valid until an `IndigoRenderer` object is created.

**Steps to Reproduce**
Using indigo-1.18.0, python 3.11

from indigo import Indigo
indigo = Indigo()
indigo.setOption("render-output-format")

**Expected behavior**
`setOption` should accept the valid parameter.

**Actual behavior**
File ".../python3.11/site-packages/indigo/indigo/indigo.py", line 140, in setOption
IndigoLib.checkResult(
File ".../site-packages/indigo/indigo/indigo_lib.py", line 1005, in checkResult
raise exception_class(IndigoLib.lib.indigoGetLastError())
indigo.indigo.indigo_exception.IndigoException: option manager: Property "render-output-format" not defined

Why does the render parameter suddenly become valid after creating a seemingly unrelated object? It is certainly unexpected that it is only possible to set a render option on the `Indigo` object _after_ creating an `IndigoRenderer`, with that indigo object as a parameter. If the option is specific to the renderer, I would expect it to be an option on the renderer object.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.