On Sat, Oct 11, 2008 at 9:19 AM, Michael Chang <email address hidden> wrote:
> I do recall there was one other issue where any X application that
> started up when X was configured for a tablet but a tablet was not
> plugged in caused warnings (usually three) to be emitted to the console.
> I think this was back around dapper, or so. There were a great deal of
> false bug reports about that.
This does not happen when HAL is used for auto detection. It DOES happen
with static conf in place in X if there is no tablet.
> While auto-detection is ideal for most (if not all) hardware, I suspect
> doing it "correctly" for wacom tablets in such a way that it doesn't
> negatively affect users who have never heard of a tablet, let alone seen
> one, will take some time and work. I suspect that some restructuring of
> both the driver and the X input infrastructure would be required.
The presence of the FDI file does not influence a user that does not have
tablet in any way. Impact is even less than having the sample conf section
in X conf or any other section. It only influences people who HAVE and
hotplug tablets and only in a positive way.
> Anyway, to answer your question, good locations to start would probably
> be in Launchpad Questions, or in a separate bug report, depending on
> your level of knowledge and expertise.
There must be a discussion about it somewhere already...
On Sat, Oct 11, 2008 at 9:19 AM, Michael Chang <email address hidden> wrote:
> I do recall there was one other issue where any X application that
> started up when X was configured for a tablet but a tablet was not
> plugged in caused warnings (usually three) to be emitted to the console.
> I think this was back around dapper, or so. There were a great deal of
> false bug reports about that.
This does not happen when HAL is used for auto detection. It DOES happen
with static conf in place in X if there is no tablet.
> While auto-detection is ideal for most (if not all) hardware, I suspect
> doing it "correctly" for wacom tablets in such a way that it doesn't
> negatively affect users who have never heard of a tablet, let alone seen
> one, will take some time and work. I suspect that some restructuring of
> both the driver and the X input infrastructure would be required.
The presence of the FDI file does not influence a user that does not have
tablet in any way. Impact is even less than having the sample conf section
in X conf or any other section. It only influences people who HAVE and
hotplug tablets and only in a positive way.
> Anyway, to answer your question, good locations to start would probably
> be in Launchpad Questions, or in a separate bug report, depending on
> your level of knowledge and expertise.
There must be a discussion about it somewhere already...
--Alexia