Book a Demo

Author Topic: Location references insufficiently rendered  (Read 3397 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Location references insufficiently rendered
« on: April 21, 2010, 02:46:13 am »
We users recently had some success at getting a number of dialogs (but not enough) to be made resizable (as they should have been in the beginning).  

This is a similar posting...

In many places in EA, there are File/Path/URL references.

They are rarely of sufficient length and certainly are inconsistent in the rendering of the reference.

This is an architectural defect.

The normal method of eliding such references is to provide the starting substring, an ellipsis, the ending substring.  The lengths of the substrings varying according to the content and control size.  In addition, the tooltip will render the ENTIRE content.

Thus:
Code: [Select]
D:\EA_WorkArea\Environment\Repository\Support\MDG\Common\Profiles\Shapescripts\Term.txtMight display (in the control) as:
Code: [Select]
D:\EA_WorkArea\...\Shapescripts\Term.txt
Perhaps we could help Sparx by locating all these defects of this type - so they can be fixed?

I got particularly hit today by the Location: control in the MDG Technologies dialog under Settings|MDG Technologies...

[edit]And over the last couple of weeks by the file controls in the MDG Profile/Technology generation process[/edit]

Reported,
Thoughts?
Paolo
« Last Edit: April 21, 2010, 03:52:56 am by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Location references insufficiently rendered
« Reply #1 on: April 23, 2010, 03:57:09 pm »
From Sparx:

I agree, displaying references in this way would be helpful.  I have submitted this as a feature request so that it is considered for implementation in a future release.

We can help Sparx by locating and documenting file references that need fixing.

In addition, we can discuss the nature of our preferred fix - length of controls (in characters), nature of the elision etc.

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!