View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002226NoesisGUIUnitypublic2021-12-31 21:372022-01-02 20:02
Reporterstonstad Assigned Tojsantos  
PrioritynormalSeverityminor 
Status resolvedResolutionno change required 
Product Version3.1.2 
Summary0002226: Noesis 3.1.2 Behavior
Description

I'm seeing new behavior in UIs which use code to assign X/Y positioning of elements within a canvas. I'm trying to understand what might be different in Noesis 3.1.x. It could be a user error on my part that is somehow manifest in Noesis 3.1.x.

  • Did viewbox functionality change, or is there new scaling behavior?
  • Did the behavior of FrameworkElement.LayoutTransform or FrameworkElement.RenderTransform change?
  • Did behavior of ScaleTransform change?
  • Does the NoesisPostprocessor import process behave differently than the prior importer, re: image centralization or transparent pixels?
  • Did handling of negative margin values change?

I'll keep testing to see if I can identify a cause on my end.

Thanks,
Shaun

Attached Files
example.png (442,987 bytes)   
example.png (442,987 bytes)   
PlatformAny

Activities

stonstad

stonstad

2021-12-31 22:00

reporter   ~0007693

Last edited: 2022-01-02 18:05

OK, disabling Noesis code (NoesisView 1349, _uiView.SetScale...) reverts behavior back to 3.0.x. What is the correct approach for disabling automatic scaling?

Separately, this raises other questions that I could not find answers to in documentation.

  • How do I read the current scale factor used by the UI?
  • Does the scale factor update dynamically when device scaling also changes (i.e. resolution change)?
  • Do I have the ability to override this automatic scaling behavior via API, i.e. if I allow the end user to configure scaling behavior?
  • Can this scaling behavior be disabled or is modification of Noesis source code the best approach?

Thanks,
Shaun
jsantos

jsantos

2022-01-02 20:02

manager   ~0007700

Last edited: 2022-01-02 20:02

Hi Shaun, as this is not a bug can we move this to the forums to continue the discussion? If there is something specific to be solved, then let's create a ticket. Thank you!

Issue History

Date Modified Username Field Change
2021-12-31 21:37 stonstad New Issue
2021-12-31 21:37 stonstad File Added: example.png
2021-12-31 22:00 stonstad Note Added: 0007693
2022-01-02 18:05 stonstad Note Edited: 0007693
2022-01-02 18:11 stonstad Description Updated
2022-01-02 20:02 jsantos Assigned To => jsantos
2022-01-02 20:02 jsantos Status new => resolved
2022-01-02 20:02 jsantos Resolution open => no change required
2022-01-02 20:02 jsantos Note Added: 0007700
2022-01-02 20:02 jsantos Note Edited: 0007700
2025-10-10 13:29 jsantos Category Unity3D => Unity