Recent shell properties error

[jupe]

Not sure if this is platform specific, and only reporting because I thought it might have other undiscovered implications, but I have noticed that using the following property now creates an error (all contexts) in recent XY versions (23.40- was ok):

e <prop System.ParsingBindContext>;

2022-08-27_054050.png

PS: Slightly off topic, but unsure why you created #Attr when Attrib already existed.

[admin]

It was never okay, but in previous versions it did not show an error message.

In the next version <prop System.ParsingBindContext> will not create an error, but it also does not return anything useful, just "[DataObject]". I don't know what you hope to be returned.

------------

Attrib?

[jupe]

I wasn't interested in the return of that property per se, it's just I had a script looping over all the shell properties, and noticed the new error as pictured, I was going to just remove that property from the loop but since it was new I thought it might have other effects in different scenarios, so reported it instead.

------------

I meant this: e <prop Attrib>;, anyway it's not important, #Attr is fine too.

[admin]

I meant this: e <prop Attrib>;, anyway it's not important, #Attr is fine too.

Wow, I'm surprised that it works. Where did you get that from? I never heard about it. Even the internet hasn't.

[jupe]

Probably on the forum somewhere, I had actually used it in the script that prompted this report. "Attributes" works too.

[admin]

Indeed it comes up one time here:
viewtopic.php?p=172363#p172363

No idea where LukeDukem got it from. This is esoteric knowledge. It is not documented anywhere in this universe.

[jupe]

That linked post is a reply to mine.

[admin]

Whoops! So you are the source. Okay, where did you get it from?