Adrian said:
You can always be more clear about things, and there will always be
people who will understand other things.
When two different people have clearly misunderstood your post, and no
other person has positively stated that they understood your post, it
would be unwise to assume you have no room for improvement.
That said, I'm still not entirely clear on what you're offering. Your
second post may have simply confused the issue, as it seems we both got
the correct impression the first time around.
[...]
Note that I'm not saying your intent wasn't honest. I'm simply saying
it wasn't immediately apparent from the post you made.
Again, I am not sure how I could have made it more clear. I disclosed
the product was made by my company, told him a viable solution where
there was not other real solution suggested, and that is all. I see
nothing 'dishonest' about it, but I will again agree to disagree here.
The "honest" comes in with respect to your intent, not your disclosure.
That is, are you really trying to help the person implement their own
code that accomplishes the same? Or do you just want to help them make
use of your own pre-packaged solution?
In a forum intended to help others with their own programming questions,
I don't find the latter to be of "honest intent". Your opinion may
vary, but in any case it's an entirely different question than the
question of "honest disclosure".
You certainly were up-front about the fact that you were offering your
product for sale. That's not what I was talking about though.
[...]
Not sure you undesrtood my post.
It seems that I did.
I do have involvement with the library
and the feature, but that doesn't mean I know how to do this "myself"
if by myself you mean not using any library.
That is what I meant, and you did not provide any indication in your
first post that in spite of being associated with a product that
implemented that functionality, you yourself had no knowledge of how to
implement it.
There's nothing wrong with you not knowing how to do it. There's not
even anything wrong with you not stating so explicitly, per se. It's
just that had you said so explicitly, it would have avoided some
confusion regarding your potential ability to help and the difference
between you refusing to help and you simply not being able to.
[...]
IMHO, assuming Bruce doesn't just copy your code wholesale, but rather
just implements his own solution based on techniques found in your
code, that would be a fine approach for him to technique. I doubt
you'd have legal standing to demand payment from him either in that
scenario.
Now really, I think we are going too much out of topic here. Why are
you speaking about my "legal standing", and why would I want to charge
him for using the code on a demo? The code for the demo is freely
available and you are expected to use it in your own programs. That is
the whole idea, and it would be silly to demand payment for that.
Well, here again is a simple misunderstanding. You wrote that "It just
puts a "biff8" object into the clipboard, or drags a biff8 object into
Excel. Just in case, Biff8 is the native file format in Excel. And the
code to do that is on the demo I mentioned, all source for the demo is
included in the file you can freely download from the page".
While your meaning is now clear, one interpretation of what you wrote is
that the code that's available is the code that "puts a 'biff8' object
into the clipboard". That is, implements the specific functionality
being requested by Bruce to solve his problem.
Instead, the code turns out to simply be example code of how to use
_your_ library to accomplish the same. With your further elaboration,
the meaning is clear, but I assure you that was not at all clear from
your previous post.
Now that you (I hope) understand how I misunderstood what you wrote, you
can understand the point of my reply. It's obviously not relevant,
since it was based on a misunderstanding.
A lot of your objection to my post seems to be regarding this point. I
hope you see now that what I wrote was perfectly reasonable given the
understanding I had, even if that understanding turned out to be
incorrect after all.
[...]
Yes. Believe it or not, I do understand that. My point is that
applications don't generally go around putting every possible format
of data onto the clipboard. An application would generally only put
Excel's format on the clipboard if there was a high expectation that
the target application would be Excel.
Well, my applications copy to the clipboard on lots of formats,
Your applications are not necessarily indicative of what most
applications require. In fact, the fact that you have seen a need to
implement BIFF support strongly suggests to me that your applications
are designed with a very specific need in mind, to operate well with Office.
Most applications do not share this need.
I would hope that it can be taken as granted that Office applications
are all written with the expectation that they will be used with each other.
and most apps I use. For example, when you copy text in
visual studio, the text is copied as RTF so you can paste formatted
code to word. But again, agree to disagree.
What does RTF have to do with BIFF? RTF is a well-documented, standard
text-formatting format understood by a wide variety of applications.
Any application that uses formatted text as a copyable piece of data is
likely to export and import RTF, and for good reason.
BIFF, on the other hand, is a very specific format for a very specific
purpose, not widely supported, and not worth messing around with unless
you have a specific need to interoperate with Excel.
How does broad support for RTF in any way justify an application also
supporting BIFF, if that application is not designed or intended to
specifically work with Excel?
[...]
On the first case, he can just disregard my post, it is not going to
help him much. In the second, what I said can be a helpful thing, and
be a better solution than saying "it isn't possible".
Yes, I agree and said as much in a previous post. It is very helpful to
know that it can be done.
However, this forum is primarily for helping other people implement
their own code. It's clear now that you don't have the information
required to go beyond the solution you offered, and there's nothing
wrong with that. My point is simply that your original post did not
make this at all clear, and IMHO you should not be surprised that it
wasn't clear.
If after all of this, you wish to remain surprised, that is of course
your prerogative. It is just my opinion, after all.
Pete