Subject:Mapper loses connections Author:Troy Hewitt Date:07 Feb 2002 06:40 PM
Stylus Studio 3.1.069k:
After mapping several (3) Source fields thru the Multiply function to the Format-Number function and then to the Target field, the center graph map does the following:
1) Several function icons don't float when the source tree is scrolled.
2) After closing the tree and re-opening, the center graph has lost 2 of 3 the mapping lines as well as the function icons.
3) Drawing an additional line from a function to an 'already mapped' target field doesn't produce an error.
Troy, Thanks for your feedback. please see my answers below:
> 1) Several function icons don't float when the source tree is
scrolled.
Function icons in the middle pane is designed not to scroll. It
is hard to come up with a good way to scroll the middle pane while you
scroll one of the schema tree...
>
> 2) After closing the tree and re-opening, the center graph has lost 2
of 3
> the mapping lines as well as the function icons.
We can't reproduce this after we fix a format-number related problem in
our internal build, but we will take a closer look after we receive your
example.
>
> 3) Drawing an additional line from a function to an 'already mapped'
> target field doesn't produce an error.
>
Drawing an additional line from a function to an 'already mapped'
target is not an error. It means the value of this target will be the
combination of the two source or user want to create a duplicate target
node...this is why you will see a context menu when you drag a line to a
already mapped target...Many users need this feature..
I believe it is related to the format-number() issue. I remapped the document using only Multiply and the issue went away.
Regarding the scrolling: When I initially built the map (just a few fields) one of the function icons DID scroll - maybe it was a fluke. This makes the working area much more clear. If I have 20, 30, 40, or 50 mappings ALL tied to one or more functions, no scrolling means my screen will be PACKED with icons and virtually unreadable. I have one client with 270 field mappings.
An algorithm that simply checks if the source or target field is on the screen would help to identify whether the icon should be displayed (just a thought).