Found some more bugs, including both my bugs:
ContainerControl height limitation - <http://support.realsoftware.com/
feedback/viewreport.php?reportid=rdkpufcf>
"ContainerControl in a composited window has refresh problems" -
<http://support.realsoftware.com/feedback/viewreport.php?
reportid=lznicdry>
"Line control in ContainerControl does not show up in built app" -
<http://support.realsoftware.com/feedback/viewreport.php?
reportid=ardrojjt>
"HTMLViewer crashes on Windows ContainerControls" - <http://
support.realsoftware.com/feedback/viewreport.php?reportid=omxkqwpc>
"Closing an embedded ContainerControl that has a mlti-line EditField
leaves the EditField scroll bars" - <http://support.realsoftware.com/
feedback/viewreport.php?reportid=qdvnhdkt>
"Calling ShowWithin against a ContainerControl crashes the built app"
- <http://support.realsoftware.com/feedback/viewreport.php?
reportid=zcizdhgy>
"Binding doesn't work for controls in ContainerControls" - <http://
support.realsoftware.com/feedback/viewreport.php?reportid=lpwvcmhq>
"pContainerControl.EmbedWithin doesn't place the new control at the
desired place" - <http://support.realsoftware.com/feedback/
viewreport.php?reportid=scslwjuh>
All of these I have been bitten by myself.
As for the feedback system itself, I find it doesn't work any more.
Examples:
<http://support.realsoftware.com/feedback/viewreport.php?
reportid=gsyoesqx> FileType MacCreator: rather than fixed it's listed
as "Closed" with a response of "This is no longer reproducible as of
2006r3a3" - as if the problem never occurred?
<http://support.realsoftware.com/feedback/viewreport.php?
reportid=eopkkjnh> HTMLViewer Crashes Mach-O: Simply "Closed" - no
response, despite being fixed according to my tests.
<http://support.realsoftware.com/feedback/viewreport.php?
reportid=eoyncwwl> HTMLViewer Cannot be Hidden: "Fixed/Implemented in
version 2006r3a1" but should be "Closed" or rather "Ignored" because
this is NOT fixed. Just look at the response: "The HTMLViewer on Mac
OS X does not support disabling, even in Cocoa."
I can go on and on. When I want to create a report, I need to search
through a list of reports by category before creating one. But what
happens when the same report is under a different category? Two
reports. And the categories are barely useful. So I bypass them
completely myself, but beside the point. 95%, my bugs don't get
looked at, let alone fixed. So what motivation is it for me to report
them, when it takes more effort to report them than to work around them?
--
Thom McGrath, <http://www.thezaz.com/>
"You don't need eyes to see, you need vision" - Maxi Jazz in
"Reverence" by Faithless
On Jul 20, 2006, at 8:54 PM, Terry Ford wrote:
On Jul 20, 2006, at 5:48 PM, Thom McGrath wrote:
I have not reported them personally because they are very specific
problems, which puts them very low on RS' priority list.
If they might affect others as well, you really should report them.
What might seem specific to you alone might not be necessarily true
as they could affect others.
Terry
PS. The best feedback RS can receive is always *your* specific
problem.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
