Our company created our own version of tables that we wanted to mimic more
closely to Excel than HTML tables. We are doing this by TLF recognizing the
table as being an InlineGraphicElement but we just replace the source with
a Sprite that has our custom table UI.
We have a ITableSelectionManager
I guess if we discover that it’s a problem, we can always revert
ISelectionManager and create a new interface for cell selection. But I agree
that it’s highly unlikely that it’s a problem.
On May 27, 2014, at 9:46 PM, Alex Harui wrote:
> That's probably fine. However, consider that some folks
That's probably fine. However, consider that some folks are using
third-party libraries that no longer have active developers so they won't
always be able to fix it. Still, I will be surprised if we break anybody.
-Alex
On 5/27/14 9:32 AM, "Harbs" wrote:
>Okay. I’m going to just implement it
Okay. I’m going to just implement it in ISelectionManager. On the odd chance
that I do break someone’s implementation, it should be a relatively easy job to
add some blank functions to honor the interface promise (assuming they don’t
need the table support).
On May 27, 2014, at 6:22 PM, Alex Ha
If someone has their own implementation of an interface, adding an API to
an interface can break them. The verifier will see that not all methods
are implemented.
It is a trade-off. You can create an ISelectionManager2 or
ITableSelectionManager to be completely safe, but the odds you will break
Adding to an API shouldn't be a problem, as long as the new
methods/properties don't change anything about the existing
implementation...
EdB
On Tue, May 27, 2014 at 12:42 PM, Harbs wrote:
> I’m working on cell selection of TLF tables.
>
> Cell selections does not fit into the normal index b
