You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When linking KSampler Config (rgthree)'s scheduler to FaceDetailer (impact-pack)'s scheduler, the link appears.
Actual Behavior
The link refuses to appear
Steps to Reproduce
the versions in cause are rgtree: v.1.0.0, and impact-pack: 8.8.1
with rgthree and impact-pack installed:
add a KSampler Config (rgthree) node;
add a FaceDetailer node;
on the FaceDetailer, right click the scheduler widget to convert to an input;
try to link the scheduler on both nodes.
Debug Logs
not required
Browser Logs
not required
Setting JSON
not required
What browsers do you use to access the UI ?
Mozilla Firefox
Other
This is probably due to the validation that the input types must match exactly.
From the impact-pack's repo, they extended the scheduler definition, causing a mismatch.
However, since all the values of the type are included in the input type, it should still be valid to link the subset to the superset.
Frontend Version
v1.8.14
Expected Behavior
When linking
KSampler Config (rgthree)
'sscheduler
toFaceDetailer (impact-pack)
'sscheduler
, the link appears.Actual Behavior
The link refuses to appear
Steps to Reproduce
the versions in cause are rgtree: v.1.0.0, and impact-pack: 8.8.1
with rgthree and impact-pack installed:
KSampler Config (rgthree)
node;FaceDetailer
node;FaceDetailer
, right click thescheduler
widget to convert to an input;Debug Logs
Browser Logs
not required
Setting JSON
not required
What browsers do you use to access the UI ?
Mozilla Firefox
Other
This is probably due to the validation that the input types must match exactly.
From the impact-pack's repo, they extended the scheduler definition, causing a mismatch.
However, since all the values of the type are included in the input type, it should still be valid to link the subset to the superset.
┆Issue is synchronized with this Notion page by Unito
The text was updated successfully, but these errors were encountered: