...[delete]...
> But that wierd thing y'all do with saving
> Custom labels by RowId in workspaces has got to go--it's a nasty
> accident waiting to happen to some poor soul some Friday afternoon.
...[delete]...
It already has:) That's why I leaving my data update to next week.
Could this problem and some other label 'features' be solved by making
the label attributes part of the table and/or map object? Each of the
labels for an object could be identified but a number (or name) and be
referenced when the layer gets drawn by the workspace. So you'd have an
object something like the following
MapObject - Labels - Label -+- Font
+- Size
+- Expression
+- Dynamic/Static
+- rotation
+- offset -+- x
+- y
... and so on.
This of course would make your databases larger, especially if you have
lots of different labels for a single object, but think of the space
saved in workspaces:)
You might even be able to give an object more than one label, without
having to add the layer to the map again.
There would be if the complete table is replaced, you would have to
transfer the labels from the old table to the new, but some sort of
automation could be done for this. The data we get a 3 monthly supply
of has static identifiers, so this wouldn't be a great problem for us.
There's probably a lot of problems which this would cause that I haven't
forseen.
- Mike Taylor
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
