MEdia Space Current Bug List

Demos.MEdiaSpaceBugTracking History

Hide minor edits - Show changes to output

Changed lines 56-57 from:
* 20091002i: I would like to get a proximity sensor working on the home node, where it progressively closes the blinds over time (say 5 minutes) if I am way, maybe putting something that says 'away' on the video, and then opens them when I return (although it should play a sound for this).
to:
* 20091002i: I would like to get a proximity sensor working on the home node, where it progressively closes the blinds over time (say 5 minutes) if I am way, maybe putting something that says 'away' on the video, and then opens them when I return (although it should play a sound for this). (added version 2.1.11)
Changed lines 29-33 from:
* 20091007: (minor but annoying) If skype is not installed, the program just crashes. It should check, and if Skype is not reachable it should
** at least warn the person and quit gracefully
** even better, start but with
the telephone button disabled (and a warning, eg., an x over the telephone button, where the tooltip says something about not being able to reach / access skype)
* 20091029: (minor) Icon for media space (home node) application doesn't exist, i.e., it just shows the generic windows icon on the desktop
* 20091002a: (serious functional) I believe there is a memory leak in the screen saver. I think this causes the office client to die when disconnected for a long time.
to:
* 20091029: (minor) Icon for media space (home node) application doesn't exist, i.e., it just shows the generic windows icon on the desktop (Resolved 2.1.9?)
* 20091002a: (serious functional) I believe there is a memory leak in
the screen saver. I think this causes the office client to die when disconnected for a long time. (Resolved 2.1.9?)
Changed line 33 from:
* 20091002h: (semi-serious). Its still possible to make the skype connection (the call button) while another person is doing the same thing. We need to put in some mechanism to ensure that one takes priority, e.g., Home node always has priority: when I click call from home, it sets the state in the dictionary, waits for a reply to be propogated, and then actually tries to establish the call. If the office node tries to establish a call during this time, it too sends it across but the home node will not allow that because it knows its trying to set up the call. This will have to be tested extensively.
to:
* 20091002h: (semi-serious). Its still possible to make the skype connection (the call button) while another person is doing the same thing. We need to put in some mechanism to ensure that one takes priority, e.g., Home node always has priority: when I click call from home, it sets the state in the dictionary, waits for a reply to be propogated, and then actually tries to establish the call. If the office node tries to establish a call during this time, it too sends it across but the home node will not allow that because it knows its trying to set up the call. This will have to be tested extensively. (Resolved 2.1.9?)
Changed lines 88-91 from:
to:
* 20091007: (minor but annoying) If skype is not installed, the program just crashes. It should check, and if Skype is not reachable it should (fixed 2.1.10)
** at least warn the person and quit gracefully
** even better, start but with the telephone button disabled (and a warning, eg., an x over the telephone button, where the tooltip says something about not being able to reach / access skype)
Added lines 29-31:
* 20091007: (minor but annoying) If skype is not installed, the program just crashes. It should check, and if Skype is not reachable it should
** at least warn the person and quit gracefully
** even better, start but with the telephone button disabled (and a warning, eg., an x over the telephone button, where the tooltip says something about not being able to reach / access skype)
Added line 29:
* 20091029: (minor) Icon for media space (home node) application doesn't exist, i.e., it just shows the generic windows icon on the desktop
Changed lines 79-87 from:
*20091016 (annoyance) Make Office node full screen
*20091006a (annoyance) Change the behaviour of Skype so it does NOT disappear when the media space is used. There are times when I need to access Skype, and it is set up to make this impossible of the media space is running.
* 20091002b: (non-serious, but gets in the way of debugging stalled video) Timestamp issues. The timestamp on the video images should be set on the sender's side to get a true indication of the time sent. As well both office and home nodes should implement this time stamp.
* 20091002c:
(non-serious, but annoying) The motion detector detects things, but I think it doesn't do the right behaviour. For example, it plays a sound when noone is there, and then fails to play a sound when someone comes in. This feature needs extensive testing in the real office environment. I suspect that the states are not being correctly triggered from particular motions.
* 20091002d: (non-serious, cosmetic) The buttons should appear on the home node as I expand the window, i.e., even over the text box. This is because I often have to rapidly answer a call, but then
have to screw around trying to make these buttons appear. Even better, it would be good to have very small buttons at the bottom (same icon images) that I can click no matter how small the screen (e.g., align this as a row on the bottom , where it shares space with the status bar). The door-open indicator can be eliminated by having the door icon reflect the current state. If I start growing the window, a one line chat box can appear, and then the two can trade off against each other.
* 20091002j: (interface fix): the text in the office node arising from
the text chat needs to be larger/viewable by someone coming in. I think its too easy to miss.
* 20091002f: (non-serious, cosmetic). On disconnect, get rid of that dialog box that says "the connection was terminated". The change of the display on the screen to Not Connected already says it all.
* 20091003l:(feature request) We need a way to restart the office node from home in case things go wrong, i.e., a quit signal that not only closes the office node
, but restarts it.
to:
*20091016 (annoyance) Make Office node full screen (fixed 2.1.8)
*20091006a (annoyance) Change the behaviour of Skype so it does NOT disappear when the media space is
used. There are times when I need to access Skype, and it is set up to make this impossible of the media space is running. (fixed 2.1.8)
* 20091002b: (non-serious, but gets in the way of debugging stalled video) Timestamp issues. The timestamp on the video images should be set on the sender's side to get a true indication of the time sent. As well both office and home nodes should implement this time stamp.
(fixed 2.1.8)
* 20091002c: (non-serious, but annoying) The motion detector detects things, but I think it doesn't do the right behaviour. For example, it plays a sound when noone is there, and then fails to play a sound when someone comes in. This feature needs extensive testing in the real office environment. I suspect that the states are not being correctly triggered from particular motions. (fixed 2.1.8)
* 20091002d: (non-serious, cosmetic) The buttons should appear on the home node as I expand the window, i.e., even over the text box. This is because I often
have to rapidly answer a call, but then have to screw around trying to make these buttons appear. Even better, it would be good to have very small buttons at the bottom (same icon images) that I can click no matter how small the screen (e.g., align this as a row on the bottom , where it shares space with the status bar). The door-open indicator can be eliminated by having the door icon reflect the current state. If I start growing the window, a one line chat box can appear, and then the two can trade off against each other. (fixed 2.1.8)
* 20091002j: (interface fix):
the text in the office node arising from the text chat needs to be larger/viewable by someone coming in. I think its too easy to miss. (fixed 2.1.8)
* 20091002f: (non-serious, cosmetic). On disconnect, get rid of that dialog box that says "the connection was terminated". The change of the display on the screen to Not Connected already says it all. (fixed 2.1.9)
* 20091003l:(feature request) We need a way to restart the office node from home in case things go wrong
, i.e., a quit signal that not only closes the office node, but restarts it. (fixed 2.1.9)
Deleted line 32:
* 20091002i: (feature request). I would like to get a proximity sensor working on the home node, where it progressively closes the blinds over time (say 5 minutes) if I am way, maybe putting something that says 'away' on the video, and then opens them when I return (although it should play a sound for this).
Changed lines 55-57 from:
* 20080609g: Text chat box should support drag and drop of external text, links, and documents
* 20080616b: Need note mechanism to display a canned or editable sticky note on the office display
to:
* 20091002i: I would like to get a proximity sensor working on the home node, where it progressively closes the blinds over time (say 5 minutes) if I am way, maybe putting something that says 'away' on the video, and then opens them when I return (although it should play a sound for this).
Deleted line 30:
* 20091002f: (non-serious, cosmetic). On disconnect, get rid of that dialog box that says "the connection was terminated". The change of the display on the screen to Not Connected already says it all.
Changed lines 35-36 from:
* 20091003l:(feature request) We need a way to restart the office node from home in case things go wrong, i.e., a quit signal that not only closes the office node, but restarts it.
to:
Changed lines 87-89 from:
to:
* 20091002f: (non-serious, cosmetic). On disconnect, get rid of that dialog box that says "the connection was terminated". The change of the display on the screen to Not Connected already says it all.
* 20091003l:(feature request) We need a way to restart the office node from home in case things go wrong, i.e., a quit signal that not only closes the office node, but restarts it.
Changed lines 27-28 from:
!!!Saul's Bugs (hispriority list)
to:
!!!Saul's Bugs (his priority list)
Deleted lines 43-44:
* 20080610b: Occasionally, the Calgary client leaves frozen images from the video feeds on screen when a crash or problem occurs elsewhere in the system (e.g., the Canmore client disconnects or is shut off suddenly)
Deleted lines 50-53:
* 20080609f: Need some way to distinguish between "pause" and "away" for video feed. Current (binary) implementation might be too coarse
* 20080610c: Need to incorporate infrastructure into project for playing sounds (perhaps different sounds on a per-event basis) at each media space node
* 20080610d: Need better notification (confirmation?) of starting a video chat, especially on the Canmore end of the link. In the current implementation, establishing an audio link can be unexpected and happen virtually without warning
Deleted lines 58-61:
* 20080609i: Implementation of document exchange needed
* 20080609k: Implementation of motion detection needed -- how this works is still somewhat up in the air, though. Using sound as a notification channel might be useful
* 20080610e: Add timestamp to streamed images
* 20080616a: Would be interesting to explore a spectrum of video awareness settings from home (e.g., available, blurry, busy/away, back shortly, off)
Changed lines 60-61 from:
* 20080616c: Need doorbell or other explicit mechanism to indicate a desire to chat on the office end
to:
Deleted lines 28-29:
*20091016 (annoyance) Make Office node full screen
*20091006a (annoyance) Change the behaviour of Skype so it does NOT disappear when the media space is used. There are times when I need to access Skype, and it is set up to make this impossible of the media space is running.
Deleted lines 29-31:
* 20091002b: (non-serious, but gets in the way of debugging stalled video) Timestamp issues. The timestamp on the video images should be set on the sender's side to get a true indication of the time sent. As well both office and home nodes should implement this time stamp.
* 20091002c: (non-serious, but annoying) The motion detector detects things, but I think it doesn't do the right behaviour. For example, it plays a sound when noone is there, and then fails to play a sound when someone comes in. This feature needs extensive testing in the real office environment. I suspect that the states are not being correctly triggered from particular motions.
* 20091002d: (non-serious, cosmetic) The buttons should appear on the home node as I expand the window, i.e., even over the text box. This is because I often have to rapidly answer a call, but then have to screw around trying to make these buttons appear. Even better, it would be good to have very small buttons at the bottom (same icon images) that I can click no matter how small the screen (e.g., align this as a row on the bottom , where it shares space with the status bar). The door-open indicator can be eliminated by having the door icon reflect the current state. If I start growing the window, a one line chat box can appear, and then the two can trade off against each other.
Deleted line 34:
* 20091002j: (interface fix): the text in the office node arising from the text chat needs to be larger/viewable by someone coming in. I think its too easy to miss.
Changed lines 94-100 from:
to:
*20091016 (annoyance) Make Office node full screen
*20091006a (annoyance) Change the behaviour of Skype so it does NOT disappear when the media space is used. There are times when I need to access Skype, and it is set up to make this impossible of the media space is running.
* 20091002b: (non-serious, but gets in the way of debugging stalled video) Timestamp issues. The timestamp on the video images should be set on the sender's side to get a true indication of the time sent. As well both office and home nodes should implement this time stamp.
* 20091002c: (non-serious, but annoying) The motion detector detects things, but I think it doesn't do the right behaviour. For example, it plays a sound when noone is there, and then fails to play a sound when someone comes in. This feature needs extensive testing in the real office environment. I suspect that the states are not being correctly triggered from particular motions.
* 20091002d: (non-serious, cosmetic) The buttons should appear on the home node as I expand the window, i.e., even over the text box. This is because I often have to rapidly answer a call, but then have to screw around trying to make these buttons appear. Even better, it would be good to have very small buttons at the bottom (same icon images) that I can click no matter how small the screen (e.g., align this as a row on the bottom , where it shares space with the status bar). The door-open indicator can be eliminated by having the door icon reflect the current state. If I start growing the window, a one line chat box can appear, and then the two can trade off against each other.
* 20091002j: (interface fix): the text in the office node arising from the text chat needs to be larger/viewable by someone coming in. I think its too easy to miss.
Added line 29:
*20091016 (annoyance) Make Office node full screen
October 05, 2009, at 09:31 AM by 136.159.7.119 -
Added line 29:
*20091006a (annoyance) Change the behaviour of Skype so it does NOT disappear when the media space is used. There are times when I need to access Skype, and it is set up to make this impossible of the media space is running.
Changed lines 39-41 from:
to:
* 20091003k: (serious): sometimes the office end does not show the home video, even though on the home end it appears as if the video is being transmitted. Disconnecting and reconnecting does not fix this.
* 20091003l:(feature request) We need a way to restart the office node from home in case things go wrong, i.e., a quit signal that not only closes the office node, but restarts it.
Changed line 32 from:
* 20091002d: (non-serious, cosmetic) The buttons should appear on the home node as I expand the window, i.e., even over the text box. This is because I often have to rapidly answer a call, but then have to screw around trying to make these buttons appear. Even better, it would be good to have very small buttons at the bottom (same icon images) that I can click no matter how small the screen (e.g., align this as a row on the bottom , where it shares space with the status bar). The door-open indicator can be eliminated by having the door icon reflect the current state.
to:
* 20091002d: (non-serious, cosmetic) The buttons should appear on the home node as I expand the window, i.e., even over the text box. This is because I often have to rapidly answer a call, but then have to screw around trying to make these buttons appear. Even better, it would be good to have very small buttons at the bottom (same icon images) that I can click no matter how small the screen (e.g., align this as a row on the bottom , where it shares space with the status bar). The door-open indicator can be eliminated by having the door icon reflect the current state. If I start growing the window, a one line chat box can appear, and then the two can trade off against each other.
Added lines 37-39:
* 20091002i: (feature request). I would like to get a proximity sensor working on the home node, where it progressively closes the blinds over time (say 5 minutes) if I am way, maybe putting something that says 'away' on the video, and then opens them when I return (although it should play a sound for this).
* 20091002j: (interface fix): the text in the office node arising from the text chat needs to be larger/viewable by someone coming in. I think its too easy to miss.
Changed lines 32-33 from:
to:
* 20091002d: (non-serious, cosmetic) The buttons should appear on the home node as I expand the window, i.e., even over the text box. This is because I often have to rapidly answer a call, but then have to screw around trying to make these buttons appear. Even better, it would be good to have very small buttons at the bottom (same icon images) that I can click no matter how small the screen (e.g., align this as a row on the bottom , where it shares space with the status bar). The door-open indicator can be eliminated by having the door icon reflect the current state.
* 20091002e: (non-serious, but functionally problematic) Video rate. I suspect that the control of video rate is NOT behaving as in the options dialog. As with the motion detector, this is likely because the states are not being correctly triggered. Also, the video flow control algorithm needs to be tested. Solution: start by testing extensively to see if there is a problem.
* 20091002f: (non-serious, cosmetic). On disconnect, get rid of that dialog box that says "the connection was terminated". The change of the display on the screen to Not Connected already says it all.
* 20091002g: (serious, intermittent, hard to reproduce). Every now and then the system connects, but doesn't display video. I can make the Skype connection, but not the video connection. Not sure what is going on.
* 20091002h: (semi-serious). Its still possible to make the skype connection (the call button) while another person is doing the same thing. We need to put in some mechanism to ensure that one takes priority, e.g., Home node always has priority: when I click call from home, it sets the state in the dictionary, waits for a reply to be propogated, and then actually tries to establish the call. If the office node tries to establish a call during this time, it too sends it across but the home node will not allow that because it knows its trying to set up the call. This will have to be tested extensively.
Changed line 17 from:
to:
* [[#sauls | Saul's Bugs]]
Changed line 25 from:
[[#critical]]
to:
[[#sauls]]
Added lines 27-37:
!!!Saul's Bugs (hispriority list)

* 20091002a: (serious functional) I believe there is a memory leak in the screen saver. I think this causes the office client to die when disconnected for a long time.
* 20091002b: (non-serious, but gets in the way of debugging stalled video) Timestamp issues. The timestamp on the video images should be set on the sender's side to get a true indication of the time sent. As well both office and home nodes should implement this time stamp.
* 20091002c: (non-serious, but annoying) The motion detector detects things, but I think it doesn't do the right behaviour. For example, it plays a sound when noone is there, and then fails to play a sound when someone comes in. This feature needs extensive testing in the real office environment. I suspect that the states are not being correctly triggered from particular motions.


>><<

[[#critical]]
>>redbox<<
Deleted line 28:
* 20080610a: Canmore client crashes when trying to re-establish an audio connection after one has been previously closed within the same session
Deleted line 37:
* 20080609c: Lots of the Phidgets stuff is hard-coded into the Canmore client; should be managed on the Calgary side and parameterized into the Constants and Variables classes for portability
Deleted line 49:
* 20080609h: Implementation of chat box needed
Deleted line 50:
* 20080609j: Implementation of utilities dialog needed
Deleted line 52:
* 20080612b: It would be good if the UI provided feedback on connection progress (and failure)
Changed lines 56-58 from:
* 20080616d: Office node should use as much of the secondary monitor (1200 x 1600) as possible
* 20080616e: Notification messages on the office node should be more descriptive
to:
Added lines 65-67:
* 20080609c: Lots of the Phidgets stuff is hard-coded into the Canmore client; should be managed on the Calgary side and parameterized into the Constants and Variables classes for portability
* 20080609h: Implementation of chat box needed
* 20080609j: Implementation of utilities dialog needed
Added line 72:
* 20080610a: Canmore client crashes when trying to re-establish an audio connection after one has been previously closed within the same session
Added line 74:
* 20080612b: It would be good if the UI provided feedback on connection progress (and failure)
Changed lines 77-79 from:
to:
* 20080616d: Office node should use as much of the secondary monitor (1200 x 1600) as possible
* 20080616e: Notification messages on the office node should be more descriptive
June 22, 2008, at 06:36 PM by 136.159.7.33 -
Changed lines 62-63 from:
to:
* 20080616e: Notification messages on the office node should be more descriptive
June 22, 2008, at 06:36 PM by 136.159.7.33 -
Changed lines 61-62 from:
to:
* 20080616d: Office node should use as much of the secondary monitor (1200 x 1600) as possible
June 22, 2008, at 06:31 PM by 136.159.7.33 -
Changed lines 58-61 from:
to:
* 20080616a: Would be interesting to explore a spectrum of video awareness settings from home (e.g., available, blurry, busy/away, back shortly, off)
* 20080616b: Need note mechanism to display a canned or editable sticky note on the office display
* 20080616c: Need doorbell or other explicit mechanism to indicate a desire to chat on the office end
June 22, 2008, at 03:36 PM by 136.159.7.33 -
Changed lines 58-59 from:
* 20080612d: UI controls should probably be consolidated (all on the top or all on the bottom)
to:
Changed lines 73-74 from:
to:
* 20080612d: UI controls should probably be consolidated (all on the top or all on the bottom; fixed version 1.2)
June 22, 2008, at 03:36 PM by 136.159.7.33 -
Deleted line 39:
* 20080609d: Canmore client should allow semantic zooming behavior on resize, eliminating redundancies among multiple forms and allowing smooth resizing between different semnatic levels. Also, minimizing app (perhaps to the taskbar) should be supported
Added line 70:
* 20080609d: Canmore client should allow semantic zooming behavior on resize, eliminating redundancies among multiple forms and allowing smooth resizing between different semnatic levels. Also, minimizing app (perhaps to the taskbar) should be supported (fixed version 1.2)
June 16, 2008, at 02:29 PM by 136.159.7.231 -
Changed line 68 from:
* 20080609b: Calgary client title bar is doing strange things -- doesn't allow user to move window (.NET framework bug caused by Calgary monitor configuration; non-trivial to fix)
to:
* 20080609b: Calgary client title bar is doing strange things -- doesn't allow user to move window (fixed version 1.2 -- thanks, Saul!)
June 15, 2008, at 09:05 PM by 68.144.37.195 -
Deleted line 28:
* 20080609b: Calgary client title bar is doing strange things -- doesn't allow user to move window
Added line 68:
* 20080609b: Calgary client title bar is doing strange things -- doesn't allow user to move window (.NET framework bug caused by Calgary monitor configuration; non-trivial to fix)
June 15, 2008, at 03:42 PM by 136.159.7.33 -
Deleted line 58:
* 20080612a: Canmore end should attempt to connect automatically on startup
Added line 72:
* 20080612a: Canmore end should attempt to connect automatically on startup (fixed version 1.2)
June 15, 2008, at 03:37 PM by 136.159.7.33 -
Changed line 40 from:
* 20080609c: Lots of the Phidgets stuff is hard-coded into the Canmore client; should be managed on the Calgary side and parameterized into the Constants and Variables classes for portability ||
to:
* 20080609c: Lots of the Phidgets stuff is hard-coded into the Canmore client; should be managed on the Calgary side and parameterized into the Constants and Variables classes for portability
June 15, 2008, at 03:36 PM by 136.159.7.33 -
Deleted line 28:
* 20080609a: Canmore client does not terminate when window is closed (thread still executing someplace)
Changed lines 41-42 from:
* 20080609d: Canmore client should allow semnatic zooming behavior on resize, eliminating redundancies among multiple forms and allowing smooth resizing between different semnatic levels. Also, minimizing app (perhaps to the taskbar) should be supported
* 20080609e: Code needs to be added to the video display windows to guarantee that the proper aspect ratio is maintained when displaying video feeds, regardless of how the client window is resized
to:
* 20080609d: Canmore client should allow semantic zooming behavior on resize, eliminating redundancies among multiple forms and allowing smooth resizing between different semnatic levels. Also, minimizing app (perhaps to the taskbar) should be supported
Deleted line 60:
* 20080612c: Mirrored video should display any time the camera is connected
Changed lines 71-74 from:
to:
* 20080609a: Canmore client does not terminate when window is closed (thread still executing someplace) (fixed version 1.2)
* 20080609e: Code needs to be added to the video display windows to guarantee that the proper aspect ratio is maintained when displaying video feeds, regardless of how the client window is resized (fixed version 1.2)
* 20080612c: Mirrored video should display any time the camera is connected (fixed version 1.2)
June 13, 2008, at 09:39 AM by 136.159.7.231 -
Changed lines 61-65 from:
to:
* 20080612a: Canmore end should attempt to connect automatically on startup
* 20080612b: It would be good if the UI provided feedback on connection progress (and failure)
* 20080612c: Mirrored video should display any time the camera is connected
* 20080612d: UI controls should probably be consolidated (all on the top or all on the bottom)
June 10, 2008, at 04:16 PM by 136.159.7.33 -
Changed lines 45-47 from:
* 20080610: Need to incorporate infrastructure into project for playing sounds (perhaps different sounds on a per-event basis) at each media space node
* 20080610: Need better notification (confirmation?) of starting a video chat, especially on the Canmore end of the link. In the current implementation, establishing an audio link can be unexpected and happen virtually without warning
to:
* 20080610c: Need to incorporate infrastructure into project for playing sounds (perhaps different sounds on a per-event basis) at each media space node
* 20080610d: Need better notification (confirmation?) of starting a video chat, especially on the Canmore end of the link. In the current implementation, establishing an audio link can be unexpected and happen virtually without warning
Changed lines 60-61 from:
to:
* 20080610e: Add timestamp to streamed images
June 10, 2008, at 04:00 PM by 136.159.7.33 -
Changed lines 23-24 from:
to:
----
June 10, 2008, at 12:44 PM by 136.159.7.33 -
Changed lines 30-32 from:
to:
* 20080610a: Canmore client crashes when trying to re-establish an audio connection after one has been previously closed within the same session
* 20080610b: Occasionally, the Calgary client leaves frozen images from the video feeds on screen when a crash or problem occurs elsewhere in the system (e.g., the Canmore client disconnects or is shut off suddenly)
Changed lines 44-46 from:
to:
* 20080610: Need to incorporate infrastructure into project for playing sounds (perhaps different sounds on a per-event basis) at each media space node
* 20080610: Need better notification (confirmation?) of starting a video chat, especially on the Canmore end of the link. In the current implementation, establishing an audio link can be unexpected and happen virtually without warning
June 10, 2008, at 12:38 PM by 136.159.7.33 -
Changed lines 11-12 from:
This page is a persistent record of all outstanding and resolved issues with the MEdia Space demo software. Please precede any new bug reports with the date they are logged, followed by a unique lowercase letter so that each bug can be managed individually. (For example, the first bug logged on 1 June 2008 would be 20080601a.)
to:
This page is a persistent record of all outstanding and resolved issues with the [[Demos/MEdiaSpace | MEdia Space demo software]]. Please precede any new bug reports with the date they are logged, followed by a unique lowercase letter so that each bug can be managed individually. (For example, the first bug logged on 1 June 2008 would be 20080601a.)
June 10, 2008, at 12:06 PM by 136.159.7.33 -
Changed lines 38-39 from:
|| border=0
||
20080609c ||Lots of the Phidgets stuff is hard-coded into the Canmore client; should be managed on the Calgary side and parameterized into the Constants and Variables classes for portability ||
to:
* 20080609c: Lots of the Phidgets stuff is hard-coded into the Canmore client; should be managed on the Calgary side and parameterized into the Constants and Variables classes for portability ||
June 10, 2008, at 12:04 PM by 136.159.7.33 -
Changed lines 38-39 from:
* 20080609c: Lots of the Phidgets stuff is hard-coded into the Canmore client; should be managed on the Calgary side and parameterized into the Constants and Variables classes for portability
to:
|| border=0
||
20080609c ||Lots of the Phidgets stuff is hard-coded into the Canmore client; should be managed on the Calgary side and parameterized into the Constants and Variables classes for portability ||
June 10, 2008, at 12:03 PM by 136.159.7.33 -
Changed lines 63-64 from:
* 20080609l: Outoging image sub-window should be draggable within the user interface (fixed 1.1)
to:
* 20080609l: Outoging image sub-window should be draggable within the user interface (fixed version 1.1)
June 10, 2008, at 12:02 PM by 136.159.7.33 -
Changed lines 28-30 from:
|| 20080609a ||Canmore client does not terminate when window is closed (thread still executing someplace) ||
||
20080609b ||Calgary client title bar is doing strange things -- doesn't allow user to move window ||
to:
* 20080609a: Canmore client does not terminate when window is closed (thread still executing someplace)
* 20080609b: Calgary client title bar is doing strange things -- doesn't allow user to move window
June 10, 2008, at 12:02 PM by 136.159.7.33 -
Changed lines 28-30 from:
|| 20080609a ||Canmore client does not terminate when window is closed (thread still executing someplace)
|| 20080609b ||Calgary client title bar is doing strange things -- doesn't allow user to move window
to:
|| 20080609a ||Canmore client does not terminate when window is closed (thread still executing someplace) ||
|| 20080609b ||Calgary client title bar is doing strange things -- doesn't allow user to move window ||
June 10, 2008, at 12:02 PM by 136.159.7.33 -
Changed lines 28-30 from:
* 20080609a: Canmore client does not terminate when window is closed (thread still executing someplace)
* 20080609b: Calgary client title bar is doing strange things -- doesn't allow user to move window
to:
|| 20080609a ||Canmore client does not terminate when window is closed (thread still executing someplace)
|| 20080609b ||Calgary client title bar is doing strange things -- doesn't allow user to move window
June 10, 2008, at 12:01 PM by 136.159.7.33 -
Changed lines 28-30 from:
|| 20080609a || Canmore client does not terminate when window is closed (thread still executing someplace) ||
||
20080609b || Calgary client title bar is doing strange things -- doesn't allow user to move window ||
to:
* 20080609a: Canmore client does not terminate when window is closed (thread still executing someplace)
* 20080609b: Calgary client title bar is doing strange things -- doesn't allow user to move window
June 10, 2008, at 12:01 PM by 136.159.7.33 -
Changed lines 28-30 from:
|| 20080609a | Canmore client does not terminate when window is closed (thread still executing someplace) ||
|| 20080609b | Calgary client title bar is doing strange things -- doesn't allow user to move window ||
to:
|| 20080609a || Canmore client does not terminate when window is closed (thread still executing someplace) ||
|| 20080609b || Calgary client title bar is doing strange things -- doesn't allow user to move window ||
June 10, 2008, at 12:00 PM by 136.159.7.33 -
Changed lines 28-30 from:
| 20080609a | Canmore client does not terminate when window is closed (thread still executing someplace) |
| 20080609b | Calgary client title bar is doing strange things -- doesn't allow user to move window |
to:
|| 20080609a | Canmore client does not terminate when window is closed (thread still executing someplace) ||
|| 20080609b | Calgary client title bar is doing strange things -- doesn't allow user to move window ||
June 10, 2008, at 12:00 PM by 136.159.7.33 -
Changed lines 28-30 from:
* 20080609a: Canmore client does not terminate when window is closed (thread still executing someplace)
* 20080609b: Calgary client title bar is doing strange things -- doesn't allow user to move window
to:
| 20080609a | Canmore client does not terminate when window is closed (thread still executing someplace) |
|
20080609b | Calgary client title bar is doing strange things -- doesn't allow user to move window |
June 10, 2008, at 12:00 PM by 136.159.7.33 -
Changed lines 28-30 from:
to:
* 20080609a: Canmore client does not terminate when window is closed (thread still executing someplace)
* 20080609b: Calgary client title bar is doing strange things -- doesn't allow user to move window
Changed lines 38-42 from:
to:
* 20080609c: Lots of the Phidgets stuff is hard-coded into the Canmore client; should be managed on the Calgary side and parameterized into the Constants and Variables classes for portability
* 20080609d: Canmore client should allow semnatic zooming behavior on resize, eliminating redundancies among multiple forms and allowing smooth resizing between different semnatic levels. Also, minimizing app (perhaps to the taskbar) should be supported
* 20080609e: Code needs to be added to the video display windows to guarantee that the proper aspect ratio is maintained when displaying video feeds, regardless of how the client window is resized
* 20080609f: Need some way to distinguish between "pause" and "away" for video feed. Current (binary) implementation might be too coarse
Changed lines 50-55 from:
to:
* 20080609g: Text chat box should support drag and drop of external text, links, and documents
* 20080609h: Implementation of chat box needed
* 20080609i: Implementation of document exchange needed
* 20080609j: Implementation of utilities dialog needed
* 20080609k: Implementation of motion detection needed -- how this works is still somewhat up in the air, though. Using sound as a notification channel might be useful
Changed lines 63-64 from:
to:
* 20080609l: Outoging image sub-window should be draggable within the user interface (fixed 1.1)
June 10, 2008, at 11:57 AM by 136.159.7.33 -
Added lines 1-53:
(:title MEdia Space Current Bug List :)
%define=box padding-left=1em padding-right=1em margin='3px 3px 0'%
%define=yellowbox box bgcolor=#fdfaea border='1px solid #ffad80'%
%define=redbox box bgcolor=#fff3f3 border='1px solid #ffc9c9'%
%define=bluebox box bgcolor=#f4fbff border='1px solid #a1cae6'%
%define=skybox box bgcolor=#f8fcff border='1px solid #aaaaaa'%
%define=greybox box bgcolor=#fbfbfb border='1px solid #aaaaaa'%
%define=greenbox box bgcolor=#e6f3e5 border='1px solid #8fd586'%
%define=whitebox box bgcolor=#ffffff border='1px solid #999999'%

This page is a persistent record of all outstanding and resolved issues with the MEdia Space demo software. Please precede any new bug reports with the date they are logged, followed by a unique lowercase letter so that each bug can be managed individually. (For example, the first bug logged on 1 June 2008 would be 20080601a.)

When closing bugs, please append the version number of the MEdia Space software that fixed the bug, for example, "(fixed version 1.1)".


!!! Contents

* [[#critical | Critical Bugs]]
* [[#noncritical | Non-Critical Bugs]]
* [[#feature | Feature Requests]]
* [[#closed | Closed Bugs]]


[[#critical]]
>>redbox<<
!!!Critical Bugs


>><<


[[#noncritical]]
>>yellowbox<<
!!!Non-Critical Bugs


>><<


[[#feature]]
>>bluebox<<
!!!Feature Requests


>><<


[[#closed]]
>>greenbox<<
!!!Closed Bugs


>><<