How can I change the default values given by the ‘Attribute User Text Functions’ panel?
It’s annoying that the dates are all in the weird month.date order.
Are you sure? Your snapshot shows 2026-09-15 and 15-Sep-26 choices and that’s just in the part of the list that shows. I’m not at my Rhino computer right now or I’d scroll the list to see if there’s more.
I would like to add to the list dd.MM.yyyy.
It’s missing that, and that’s the one I always use.
Even d.M.yyyy would be an improvement.
Double click on the function icon against the text entry you want to format:
That brings up an edit window. Add the formatting you want inside the first field quotes within the brackets:
Tedious if you have a lot of fields though.
HTH
Jeremy
Don’t let the fact I got the yyyy format wrong put you off!
I would like emphasize that my question was not about inserting or editing the values. My question is, how can I modify the defaults?
You edit the values format and save the file as template over the default template you use.
Can you walk me through the process?
How do you edit the default values?
Bump
@Gijs @wim @theoutside
How and where to modify the content of this default list?
This list is just a template for the formating, there is pretty much all variations of it
But, if you need to create a custom one anyways, you can using something like this, however, you do not edit inside the standard Date, all you have to do is create a custom Document User Text with the formatting like the image below, with the name Date, like on the second image.
![]()
So when you press enter, it updates to the current date
![]()
And on your title block, or wherever you are trying to use it, you call it like a DocumentText variable
Then, to make it easier to edit, because I like to have a few stuff manually editable, you can activate the Document User Text on the side panel, and have everything there editable (for those that you are not using the formulas at least.
My drawing title and edges are all in a block with this variables in and they update based on the file using this panel, so if I have to change/update my drawing block it goes everywhere, and the nice part, when I open an old drawing, it asks if it should be updated or not because I have it Embedded and Linked.
So, after you finish creating your custom Document User Text you take this file and Save as a Template
And when you press New and it asks you to choose a template, you mark the box so it is the default template when Rhino opens

This way you have all the custom text loaded in all new files.
If you need to insert this Custom Document User Texts into existing files you can do it by importing them from the Template file you just created.
I don’t know if this is the right way to do it, but this is how I have done and it is working for me like a charm.
You can also do something similar using Block Text Atributes, but them you have to select the block and edit on the properties and stuff, so, for layout blocks, I prefer to have this on Document User Text.
Now, Welding callouts and this kind of stuff I have on Block Attributes, because each one is unique.
edit. Sorry, had to edit because I submited before finish writting by accident.
I realise my question is maybe hard to understand, as it may be interpreted in various simplified ways.
I try to be super clear this time.
This is list of default options, that live in e.g. Options/Text Field/Date.
This list lives somewhere in Rhino-settings or maybe as a text file in the installation folder. It contains the predefined templates for assigning date/time functions. I am fully aware that this list is not exhaustive, and I can make my own versions from scratch even. This is what I have done.
But my question is - How can I modify this list of predefined samples, so I could add my own predefined shortcut to this list?
If there was a way to edit the Default/Predefined list it wouldn’t be called Default/Predefined don’t you think? That is the whole purpose of Document User Text existance…
Again, you are misundestanding the question.
Asked Claude:
Where it comes from
The functions you see in the fx picker (Date, Area, FileName, BlockInstanceCount, DocumentText, ObjectLayer, PageNumber, etc.) are implemented as native code in Rhino’s core, with a subset also exposed in RhinoCommon as static methods on Rhino.Runtime.TextFields (e.g. DocumentText(string key), BlockAttributeText(...), ObjectLayer(string id), ObjectPageName(string id), BlockName(string blockId) — these last three were added in Rhino 8 alongside the “Enhanced Text Fields” work). The picker’s list is almost certainly built by enumerating that fixed set at the UI layer — there’s no external XML/JSON/ini template file shipping alongside Rhino that defines these entries the way, say, a Grasshopper template folder does for the script editor.
Can it be modified
Not through Options or any file on disk that I could find — it’s baked into the compiled executable/RhinoCommon.dll for that version of Rhino.
Hej Toni -
If you ask me, this just doesn’t work.
I’ll get it on the list.
Thanks.
-wim
→ RH-99391 TextField: Date Format - Current Region
Hi @Toni_Osterlund,
While the available option list can’t currently be added to, it is easy enough to add a command to Rhino to apply an Attribute User Text Date field correctly formatted as dd.MM.yyyy to any pre-selected object - or objects, as it can be done in bulk - with a single click.
When applied to a Date field with different formatting it will change it to the new format. The dates are correctly set as function outputs, not plain text, so they continue to work with the fx button.
If this is of interest to you, you’ll find it in the package manager under TOdotDate (check the pre-release box):
There’s one command available: TOAddDotDate plus icons so you can put it on a menu bar.
![]()
Regards
Jeremy
Hi @jeremy5
and thank you for your extended efforts on this matter.
Thinking about the method that you’ve constructed as a plugin - I think it can be handled by a macro as well. And also stored as a button.
!_SetUserText _Pause Date %<Date('dd.MM.yyyy')>% _Enter
That’s a lot simpler. One thing: to match what the function creates you need a second field with your current locale, similar to ‘en-UK’ depending on where you are.
Regards
Jeremy










