Difference between revisions of "Documentation:Windows Section 6"

From POV-Wiki
Jump to navigation Jump to search
m (itc)
Line 11: Line 11:
  
 
<p>
 
<p>
Before submitting any bug reports, make sure that the bug is not in the list of known bugs  
+
Before submitting any bug reports to our forums, make sure that the bug is not already listed on our [http://bugs.povray.org/ bug tracker].
below. Please remember that the POV-Ray users who provide assistance on our news server are  
+
Please remember that the POV-Ray users who provide assistance on our forums are volunteers who give their time for free so you
volunteers who give their time for free so you can enjoy this program for no charge. Keep this  
+
can enjoy this program for no charge. Keep this in mind when wording your message.
in mind when wording your message.
 
 
</p>
 
</p>
  
 
<p>
 
<p>
MAKE ABSOLUTELY SURE that the subject of your report isn't already covered in this document.  
+
Make sure that the subject of your report isn't already covered in this document.
Questions that are already answered either in this help file, any README's, installation
+
We also <strong>strongly recommend</strong> that you check out the online version of the  
notes, FAQ's, or other files supplied with this program will most likely not get the reply
 
you expect.
 
</p>
 
 
 
<p>
 
We <strong>strongly recommend</strong> that you check out the online version of the  
 
 
[http://wiki.povray.org/content/Knowledgebase:POV-Ray_Questions_and_Tips POV-Ray Questions and Tips]
 
[http://wiki.povray.org/content/Knowledgebase:POV-Ray_Questions_and_Tips POV-Ray Questions and Tips]
 
before submitting a report.
 
before submitting a report.
</p>
 
 
===Feature Requests are not bugs===
 
<p>
 
If you  want to request a feature, we recommend you first discuss it in one of the povray groups on our [http://news.povray.org/ news server].
 
</p>
 
 
===Known Bugs===
 
<p>
 
If you select an entire group of files and then drop them into povray, the first and last
 
files will switch places. This is a bug in the way things are handled by Windows and not a bug
 
in POV-Ray for Windows.
 
</p>
 
 
<p>
 
Other known issues can be found in the [http://wiki.povray.org/content/Knowledgebase:POV-Ray_Questions_and_Tips POV-Ray Questions and Tips].
 
 
</p>
 
</p>
  
Line 53: Line 30:
  
 
<p>
 
<p>
To do this, go to the GUI Extensions menu, and deselect 'Use Extensions'. Then exit and  
+
To do this, go to the GUI Extensions sub-menu of the Options menu, and deselect 'Use Extensions'. Then exit and  
 
restart POV-Ray for Windows. The GUI Extensions menu should then state 'No Extensions Loaded'  
 
restart POV-Ray for Windows. The GUI Extensions menu should then state 'No Extensions Loaded'  
 
(it may already do this if you've got none installed). Then attempt to duplicate the problem  
 
(it may already do this if you've got none installed). Then attempt to duplicate the problem  
Line 60: Line 37:
  
 
===Crash Upload Utility===
 
===Crash Upload Utility===
<p> In order to assist the team in tracking down crashes, Structured Exception Handling and mini-dump generation capabilities have been added to povray for windows. After an unhandled exception POVWIN will now offer the option of creating a mini-dump (brief or full) for submission.</p>
+
<p> In order to assist the team in tracking down crashes, Structured Exception Handling and mini-dump generation capabilities have been added. After an unhandled exception POVWIN will now offer the option of creating a mini-dump (brief or full) for submission either manually or via the crash upload utility which is installed with the program.
<p class="Note"><strong>Note:</strong> The crash upload utility automates this process for the mini-dumps, but not for the full dumps.</p>
 
 
 
===Bug Reporting via Email===
 
<p>
 
Please use the POV-Ray news forums or the bug reporting system.
 
 
</p>
 
</p>
  
Line 77: Line 49:
 
</p>
 
</p>
  
<p>Any messages or reports sent to us may be re-posted in our newsgroups, on USENET, or on our web site, if we consider it appropriate to do so.</p>
+
<p>Any messages or reports sent to us may be re-posted in our forums, bug tracker, or our web site if we consider it appropriate to do so. We will in such cases of course remove any obvious identifying or personal information first.</p>
  
 
<p>You should not expect any reply to bug reports. If you wish to follow the progress of a bug, it's best to use the bug tracker (be sure to configure your account to receive notifications of replies to your bug). You can also request to be emailed when there are replies to an existing bug report.</p>
 
<p>You should not expect any reply to bug reports. If you wish to follow the progress of a bug, it's best to use the bug tracker (be sure to configure your account to receive notifications of replies to your bug). You can also request to be emailed when there are replies to an existing bug report.</p>
Line 88: Line 60:
 
<li>The version number of POV-Ray for Windows. You can see this by selecting About from the Help Menu.</li>
 
<li>The version number of POV-Ray for Windows. You can see this by selecting About from the Help Menu.</li>
  
<li>Your operating system. We need to know what version of Windows you are running
+
<li>Your operating system. We need to know what version of Windows you are running.
  
 
<li>Your computer ; what processor and how much memory.</li>
 
<li>Your computer ; what processor and how much memory.</li>
Line 94: Line 66:
 
<li>A complete description of the problem and what led up to it. It will make it a <strong>lot easier to track a bug down</strong> if you can include a scene file that will cause the problem. If the file is large, try removing parts until you have the minimum scene file that will cause the problem.</li>
 
<li>A complete description of the problem and what led up to it. It will make it a <strong>lot easier to track a bug down</strong> if you can include a scene file that will cause the problem. If the file is large, try removing parts until you have the minimum scene file that will cause the problem.</li>
 
</ol>
 
</ol>
 
<p class="Warning"><strong>Note:</strong> If posting on the news group or emailing someone for support, do not include file attachments without asking first. This <em>particularly</em> applies to email (for security purposes, emails with unsolicited attachments may be deleted unread). Reasonably-sized file attachments on the bug tracking system are permitted.</p>
 
  
 
<!--<wikinav>--->
 
<!--<wikinav>--->

Revision as of 20:49, 29 January 2013

This document is protected, so submissions, corrections and discussions should be held on this documents talk page.


Bug Reports

Before submitting any bug reports to our forums, make sure that the bug is not already listed on our bug tracker. Please remember that the POV-Ray users who provide assistance on our forums are volunteers who give their time for free so you can enjoy this program for no charge. Keep this in mind when wording your message.

Make sure that the subject of your report isn't already covered in this document. We also strongly recommend that you check out the online version of the POV-Ray Questions and Tips before submitting a report.

Bugs and GUI Extensions

If you have installed any GUI Extensions (or used any software that may have installed them), make sure you see if the problem exists with the extensions disabled and unloaded.

To do this, go to the GUI Extensions sub-menu of the Options menu, and deselect 'Use Extensions'. Then exit and restart POV-Ray for Windows. The GUI Extensions menu should then state 'No Extensions Loaded' (it may already do this if you've got none installed). Then attempt to duplicate the problem again.

Crash Upload Utility

In order to assist the team in tracking down crashes, Structured Exception Handling and mini-dump generation capabilities have been added. After an unhandled exception POVWIN will now offer the option of creating a mini-dump (brief or full) for submission either manually or via the crash upload utility which is installed with the program.

Bug Reporting via our Bug Tracking System

Bug reports may be lodged about POVWIN by using the bug tracking system. The bugtracker is monitored regularly by the POV-Ray development team and they will address any properly-lodged bug reports in the most timely manner possible.

You may like to remember, however, that no matter where you end up getting assistance from, users who show that they have looked in the documentation and read the POV-Ray Questions and Tips first, will be much more likely to receive the response they want than someone who obviously has not done their homework. It's also important to check that the bug hasn't already been reported - if it has, and is still open, don't add a new report - if you have relevant information not already in the existing report, consider adding a comment.

Any messages or reports sent to us may be re-posted in our forums, bug tracker, or our web site if we consider it appropriate to do so. We will in such cases of course remove any obvious identifying or personal information first.

You should not expect any reply to bug reports. If you wish to follow the progress of a bug, it's best to use the bug tracker (be sure to configure your account to receive notifications of replies to your bug). You can also request to be emailed when there are replies to an existing bug report.

The minimum information to include in your bug report is

  1. The version number of POV-Ray for Windows. You can see this by selecting About from the Help Menu.
  2. Your operating system. We need to know what version of Windows you are running.
  3. Your computer ; what processor and how much memory.
  4. A complete description of the problem and what led up to it. It will make it a lot easier to track a bug down if you can include a scene file that will cause the problem. If the file is large, try removing parts until you have the minimum scene file that will cause the problem.


Menus Speed Considerations


This document is protected, so submissions, corrections and discussions should be held on this documents talk page.