View Issue Details

IDProjectCategoryView StatusLast Update
0004176NoesisGUIStudiopublic2025-05-20 12:14
Reporterdstewart Assigned Tosfernandez  
PrioritynormalSeverityminor 
Status assignedResolutionopen 
Product VersionStudio_Beta 
Target VersionStudio_Beta 
Summary0004176: Number Variants Are Difficult To Identify Without A Programming Background
Description

[This Ticket should be logged as Feedback and not a Bug]

Currently, we present many ways to refer to what to a Designer is just a 'Number'.

−> In Data, we call it a "Number".

−> In DynamicProperties, we call it an "Integer" or a "Float".

−> In Resources, we call it an "Int32/Int16" or a "Single/Double".

For users who are unfamiliar with the technicality of number types, this can sometimes result in a blocker. This is especially the case when creating a new Resource from the Resources Panel, where the terms "Number", "Integer", and "Float" all yield no results.


Suggestion:

In the Resources Panel, renaming to:

"Single (Number: Float)"
"Double (Number: Precise Float)"

Int16 (Number: 16-Bit Integer)
Int32 (Number: 32-Bit Integer)

UIInt16 (Number: 16-Bit Integer)
UIInt32 (Number: 32-Bit Integer)

In this syntax, users would be able to get a positive Search Result whether they typed the Uber-Technical Name (Double/Single/Int), the Somewhat Technical Name (Integer/Float), or the Layman's Name (Number).


In the DynamicProperties Configuration, renaming to:

"Integer (Number)"
"Float (Number)"

PlatformAny

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2025-05-19 15:39 dstewart New Issue
2025-05-19 15:41 dstewart Description Updated
2025-05-20 12:13 jsantos Assigned To => sfernandez
2025-05-20 12:13 jsantos Status new => assigned
2025-05-20 12:14 jsantos Target Version => Studio_Beta