Include default text examples in the "C Syntax" dialog

[plafosse]

Leaving the old description but summarizing a more concise list of features we'd still like to add (some have already been addressed):

• Link to documentation for the types (which includes the additional expressions beyond standard C)
• Include default text in the "C Syntax" dialog (default text that disappears as soon as any manual text is entered)
• Clarify the default base for the structure size dialog is hexadecimal (tracked now in Inconsistent hex/integer input boxes #5836)

---

Current problem is that its not super intuitive how to add new structures to the TypeView. You have to select one of the following menu items:

Its not clear that one of these is for creating types with C syntax and the others will create a type of a given size.
Its also not clear how to create an enumeration.

Additionally once the "Create Types" is selected it prompts you with an empty box and tells you C Syntax which though descriptive isn't exactly helpful.

Here are a number of suggestions on how to remedy:

1. Combine the "Create Types" and "Create Structure/Union" dialogs
2. The default text in the "C Syntax" should provide examples.
3. There needs to be some indicator that what is being parsed is more expressive than C and what those expressions are

• __offset, __packed, ` escaping, emoji, etc

4. Perhaps a sidebar with links to additional documentation.

[plafosse]

Additionally "Create New Structure" window accepts hex by default without any indication. This should be refactored so its obvious

[fuzyll]

We may benefit from having a separate issue to track the hex thing. This is not the only time/location where a user might expect a value to be interpreted as decimal and be surprised when it isn't.

One option is for us to stick some hint (like a ghosted-out 0x to the left of the number that’s being entered) that lets the user know how we are going to interpret their input. (Bonus points if, when I type 0n, it changes the ghosted out 0x to the solid 0n. Extra bonus points if I can somehow click the 0x to open a small base-picker thing to change the base.)

I think we do a great job at being consistent in the UI, but not every other tool out there defaults to hex (or is as consistent), so this still trips users up. The above suggestion also addresses the relative un-discoverability of using 0n to specify a demical input.

[psifertex]

Check box 2 and 3 are implemented in builds >= 4.2.5846

[fuzyll]

Just going to close this as completed in 4.2.5846. Linking to the documentation isn't something we really do in menus right now and probably warrants a wider pass to look at later. The other remaining problem is already its own separate issue.

[0xdevalias]

Linking to the documentation isn't something we really do in menus right now and probably warrants a wider pass to look at later.

@fuzyll Should a more general issue be created to track that aspect/potential for future?