Create a Dictionary UDF which creates a Scripting.Dictionary object

[aemcasa@…]

Dictionaries are a very common and useful type of data container. In this Trac database and in the AutoIt forums there descriptions of several ways in which dictionary objects can be created in AutoIt.

In particular in the issue #61 of this Trac database there is an explanation of how to use the Scripting.Dictionary class and the ObjCreate() function to create a Dictionary object.

While this is a good solution, which seems to work on all versions of windows, it suffers from the fact that it is not built into AutoIt. Thus I propose that a very simple Dictionary UDF should be created and added to the AutoIt standard library. This UDF would basically contain a single function, Dictionary(), which would return a Dictionary object. Additional helper functions could be added to simply tasks such as Dictionary to string conversion and viceversa, etc.

I would be willing to create this UDF library. I just need to know whether it would be acceptable to do so (assuming that it passes the required code and documentation quality).

[TicketCleanup]

Automatic ticket cleanup.

[Angel]

I submitted this feature request twice by mistake. The second one is the valid one, since it is correctly linked to the "Standard UDF" component.

I see that this has been deleted by "TicketCleanup". I do not know why or what that means. Please let me know what I should do to properly create a ticket.

Cheers,

Angel

[Valik]

So... do you not see the big giant red box that appears when you try to create a new ticket?

[Angel]

Replying to Valik:

So... do you not see the big giant red box that appears when you try to create a new ticket?

Hi Valik, always a pleasure being commentslapped by you ;-)

I actually did not try to reopen the ticket. I clicked Done and I immediately realized that the component was set to AutoIt rather than to Standard UDF as it should. I clicked stop on my web browser thinking that the ticket had not been sent yet. I changed it and sent it again. Sorry!

So what should I do now? You Rejected the first ticket (1490) as well. Is it because of this mistake or because you do not think that the request has any merit?

[Valik]

I closed it because of this line which you can find on WikiStart:

Don't ask the developers to write UDFs. If you want to see UDFs added then you'll need to write it or get someone else to write it and submit it with the proper documentation.

[Angel]

Valik,

I am definitely not asking the developers to write the code. In fact I already have some of the code written.

In fact, in the feature request I said:

"I would be willing to create this UDF library. I just need to know whether it would be acceptable to do so (assuming that it passes the required code and documentation quality)."

What I don't know is to whom should I send the code for review once I believe it is in good shape (including the documentation, of course).

[Valik]

The forum exists for a reason. We shouldn't just add code that somebody brings in off the street. We should add code that is tested by the community and something they are already familiar with.

[Angel]

Replying to Valik:

The forum exists for a reason. We shouldn't just add code that somebody brings in off the street. We should add code that is tested by the community and something they are already familiar with.

Ok, thank you. I will bring it up in the forums and see if other people like it or even agree with the idea of adding such a UDF. If I see that there is some interest I will open a new feature request if that is all right.