Component description

[MichaelT_123]

Hi TF360,

Since the introduction of "Hub improvement", there is a problem with fetching:

component.description

property.

The debug traceback is:

3 : Description cannot be fetched while offline

File "....f782/Api/Python/packages\adsk\fusion.py", line 84589, in _get_description
return _fusion.Component__get_description(self)

This is anathema to well-established API script practices, flipping code pyramids upside down.

Even ancient Egyptian could not be capable of doing that!

There is also the issue with:

Getting attribute Component.partNumber

from copy/paste_new component unless the design is saved and reopened, obviously in online mode.

Regards

MichaelT

[MichaelT_123]

Hi TF360,

 Is there any chance in a reasonable timeframe that the:

    return _fusion.Component__get_description(self)

           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^

RuntimeError: 3 : Description cannot be fetched while offline

be fixed, allowing offline usage of the Fusion?

Regards

MichaelT

[MichaelT_123]

Hi TF360,

I am not sure if you identified the problems, but I think I found at least one.

The:

component.description

property is "dangling"; it is not initialized. It perhaps happens when the underlying component is empty, like just created NewComponent.

Perhaps there are other 'inconsistencies' in the surrounding code that were introduced after the recent 'Hub' update.

In the above-mentioned case, setting 

component.description = ''

should alleviate the issue... without lifting even a single block of the pyramid.

Regards

MichaelT

[MichaelT_123 · Accepted solution]

Hi TF360, FusionForumFellows (FFFs),

I have received a private message from the Honorable Mr/Mrs/Ir/Irs Closed-Loop-Bot stating that the "Component Description" problem has been resolved; thus, after a limited number of tests, I hesitantly award the resolution The Status of Solution.

Regards

MichaelT 

[MichaelT_123]

Hi Mr/Mrs/Ir/Irs Closed-Loop-Bot, TF360, FusionForumFellows (FFFs),

Although I hesitantly awarded the resolution The Status of Solution"    

the problem still persists:

  File "....b5224/Api/Python/packages\adsk\fusion.py", line 89200, in _get_description

    return _fusion.Component__get_description(self)

           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^

RuntimeError: 3 : Description cannot be fetched while offline

Suggestion for whoever "delivered the resolution" ...

Please diligently check  my suggestion from the previous post:

"property is "dangling"; it is not initialized."  

Make sure that in ANY PHASE of the component object's existence, the <description> property IS INITIALIZED.

Particularly, debug the outcome of returnValue = occurrences_var.addNewComponent(transform).

Always keep the property reference LOCAL as a MASTER and synchronize it with the respective CLOUD INSTANCE at a convenient time.

Regards

MichaelT

[BrianEkins]

I've been told that this behavior is to be expected with the changes they've made to the description and part number. I guess the solution is to check if the user is online or not and if they're not then warn them and not perform the operation.

I'm not defending the new behavior, just passing on what I was told.

[MichaelT_123]

Hi Mr Brian Ekins,

Thank you for your effort/input into the problem.

In particular, I appreciate that you courageously put your real name/identity behind the post.

This is less common these days, as we see anonymous AI in our interactions with the real and the Matrix-like world... increasingly frequently.

The latter creates a "legal vacuum" as the "interlocutor" has no bearings in the (current) legal system(s).

Currently and in the past, we have/had many choices of response/interactions with "authorities" delivering the message:

• nod a head
• turn back and walk away
• slap at the right cheek and wait for the left to be presented
• throw messenger out of a window (Kremlin)
• shorten the emissary by the head (Robespierre)
• present three compassionate choices: beheading, hanging, drowning (Tower of London)
• invite to Xerxes Royal Banquet …
• …

The list "How responses were carried out?" is long, and it shows an extra-intelligent level of innovation.

However, one lingering, very important question remains.

What to do with AI, as in my recent encounter with Closed-Loop-Bot, Honorable, of course?

• nod a head - pointless
• turn back and walk away – in which direction
• slap at the right chin and wait for the left to be presented – illusory option
• throw messenger out of a window – will not fall anyway
• shorten the emissary by the head – how to locate the head?
• present three compassionate choices: beheading, hanging, drowning (Tower of London) – preposterous for AI being
• invite to Xerxes Royal Banquet – it is a fictitious story anyway, perpetrated by… Greeks
• …

So are dilemmas…!!!

Sorry, Mr Ekins, for this hyperbolic digression, but I could not hold myself back 😊

Regarding the comparatively insignificant problem at hand, a fault in accessing

component.description  property in offline mode, I want to point out that:

• Fusion was promised as offline and online software.
• The API description of the component.description  property does not state any restrictions
• The relevant API component has been in operation, perhaps since the software's interception in the public space.
• Many users embedded this particular API reference in their designs/code.
• The recent arbitrary change… skillfully flips the code pyramid upside down, which was not even in the dreams of the Ancient Egyptians, as per the latest archeological discoveries.

I hope you understand why I will refrain from congratulating TF360 on such an achievement.

As usual, it was nice talking with you, Mr. Ekins.

With Regards

MichaelT

[MichaelT_123]

Hi TF360,

Please treat this post as an EMERGENCY.

I recently checked a not-too-old design and found that the component's description property content has changed!!!

It contained the description from another design, a completely unrelated design. I inspected other designs... only to discover that most of them have been meticulously shuffled, like at a good casino poker table. I haven't found any pattern; it seems to be random replacements of the description property string from other components.

I can not pinpoint when this happened, but I suspect the mishap occurred during the new hab development, introduced with fanfare (and my complaints) not long ago.

I use the component's description property as the active input/element in the design process.

That means hundreds (perhaps thousands) of components in my work over the years were compromised.

SERIOUS QUESTION TO TF360!

DO YOU HAVE THE ABILITY TO RESTORE MY FILES TO THE CONDITION BEFORE THIS MALICIOUS COMPONENT DESCRIPTION SHUFFLE?

Sincerely,

MichaelT

PS.

As a backup, I will post a link to this post on the Support Forum. 

Ref: https://forums.autodesk.com/t5/fusion-support-forum/emergency/td-p/14342914

[hettematechniek]

This is not going to change, it's caused by shared part number, it searches to identical partnumbers, the first ever made becomes the master, al the others become shared part numbers of the master and are given the same description as the master. Autodesk desided that you are not allowed to use the same part numbers for different parts. So all your work is messed up and there is no way back. The lack of performance that comes with it is for free. So I'm switching (after 30 years Autodesk) to Alibre design, complete ofline and full ownership, max control over your own data.

@hettematechniek-this post has been edited due to Community Rules & Etiquette violation.