TypeError when calling .Show() on a TaskDialog - Anywhere to track this issue?

[sstewart]

I’ve found a few threads that highlight this issue:

AttributeError: object 'TaskDialog' has no attribute 'Show'

Since today i’m getting an error when i’m running this script in Revit 2023.1 Is was always working for 100% in Revit 2021, 2022, 2023, ending with a dialog. I did no changes for weeks. Does anybody know what’s going wrong? test pin-palen_script.dyn (12,2 KB) [image] import clr #add a reference to the Revit UI .dll so we can access the UI Namespace... clr.AddReference('RevitAPIUI') #import everything from the UI Namespace... from Autodesk.Revit.UI import * #IN Variabele #hoogtes = IN[0] m…

Python 2 to Python 3 error

Annoying, you don’t have to use iselection, unfortunately not as satisfactory… but still does a job… #credit to the forum for code import clr import sys import System clr.AddReference('RevitAPI') import Autodesk from Autodesk.Revit.DB import * import Autodesk.Revit.DB as DB clr.AddReference('RevitAPIUI') from Autodesk.Revit.UI import * from Autodesk.Revit.UI.Selection import * from System.Collections.Generic import List from RevitServices.Persistence import DocumentManager doc = DocumentM…

As well as this on GitHub:

TypeError : No method matches given arguments for Show(), called on TaskDialog Object

Looks like the issue is being tracked internally now, I was wondering if anyone knew if there was a place I could watch this issue for a resolution. I can work in IronPython for now, but would like to know if/when I can update the script to CPython.

[jacob.small]

Subscribe to notifications to the github issue and you’ll get all the notifications. You can also test future builds in the daily builds on DynamoBuilds.com.

[sstewart]

I wasn’t able to access to the link in the Git response. Is it safe to assume they will update the open issue I linked to with whatever updates come along/whenever it’s fixed?

[jacob.small]

@sstewart

I wasn’t able to access to the link in the Git response.

You don’t need that link, as it’s internal to ADSK developers in a private development management tool. The issue on the public Github will eventually be closed as ‘fixed’, ‘duplicate’ (in which case follow the original), or ‘won’t fox’ (in which case ask for some insight on why in the github).

[sstewart]

Okay, thank you!