------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=127223
kde.org eternaldusk com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|FIXED |
------- Additional Comments From kde.org eternaldusk com 2006-05-18 06:26
-------
The fix worked... sort of. It got rid of the grey, but revealed another
(possibly related?) problem:
I went into the configure menu, adjust my cam settings, closed the config
dialog, re-open it, and verified that the setting were still there and
everything looked good. No problem so far...
However, when I next try to open a yahoo conversation, both the preview window
and the receiving window show super high brightness/contrast - as if the yahoo
plugin is not initializing them with the values from the configuration dialog.
Even more - I tried turning auto-brightness/contrast on before-hand and it
seems to have no effect on the preview or stream.
I can go to the configuration dialog and adjust the values while I have a
stream going. If I do, the preview and reception window will then show the
correct vid. But, the next time I start a test session (without the
configuration dialog up), the exact same thing happens (window starts out
ultra-bright/contrast).
This wouldn't be so much of a problem, but there seems to be a second bug: If
you start a stream, then adjust the video with the configuration dialog (fixing
the stream), then *close* the *configuration* dialog, the sending stream (and
preview window) continues streaming only the last frame captured before you hit
the close button.
Re-opening the configuration dialog seems to get the stream going again, but
kopete seems to run dog-slow if you keep both a cam stream and the
configuration dialog open at the same time. Closing the configuration dialog,
again seems to stop it from capturing frames.
It seems as if the configuration dialog is sending a command to V4L to quit
capturing frames when you close it - regardless of the capture state when you
opened the configuration dialog. If that's the case, it shouldn't be too hard
to save the initial state and restore it at close, yes?
Thanks again for your time,
-J
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel
