[Ffmpeg-devel] [PATCH] Correct inttypes.h emulation for VisualStudio
Tue Dec 5 22:53:25 CET 2006
Corey Hickey <bugfood-ml at fatooh.org> writes:
> M?ns Rullg?rd wrote:
>> Corey Hickey <bugfood-ml at fatooh.org> writes:
>>> Reimar D?ffinger wrote:
>>>>>>> As far as I know, none of the FFmpeg developers is a regular MSVC user.
>>>>>> Any developper who admits to be, will probably be tarred and
>>>>>> feathered and kicked out.
>>>>> A team has to have its standards.
>>>> Damn. Now I'm in trouble. I actually used the C# variant. Will you
>>>> accept my excuse that I only used it because I had to make a Gui app
>>>> that uses the serial port? Anyone who tried to use/program serial port under
>>>> windows should be able to feel with me ;-).
>>> Ick. :)
>>> There's a computer where I work that has two onboard serial
>>> ports. Windows calls them both COM2, and it can't use either of them.
>> It's sometimes possible to change the numbering from the device
> At the time, as far as I could tell, changing it within the device
> manager was not possible (I did look, but I don't remember the
> details). I just plugged in a USB-->serial adapter and used that
What annoys be with USB-serial adapters in windows is that each time
you plug it in, the COM number gets incremented, soon becoming
inaccessible from programs that only offer a choice of COM1-4, and
eventually stops working entirely when it reaches some maximum value.
> This is off-topic, though; I just thought it was mildly amusing. :)
It's amusing alright, as long as it's happening to someone else...
mru at inprovide.com
More information about the ffmpeg-devel