Timeline for Screen objects sometimes not rendering
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 12, 2018 at 9:18 | history | edited | Philipp |
This appears to be a purely technical issue unrelated to the design of your game.
|
|
| Nov 11, 2018 at 14:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 11, 2018 at 6:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Sep 7, 2018 at 1:20 | comment | added | Stack Exchange Broke The Law | Swing (and AWT) is not designed for multithreading. Weird things can happen when you use multithreading with Swing. If you want multithreading don't use Swing. If you want Swing don't use multithreading. | |
| Sep 7, 2018 at 1:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 6, 2018 at 22:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 6, 2018 at 23:27 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 2, 2018 at 15:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| S Apr 19, 2018 at 19:10 | history | suggested | Rodia | CC BY-SA 3.0 |
Removed "0 down vote favorite" at the beginning
|
| Apr 19, 2018 at 1:10 | review | Suggested edits | |||
| S Apr 19, 2018 at 19:10 | |||||
| Apr 19, 2018 at 1:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 12, 2018 at 14:44 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 8, 2018 at 21:43 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 19, 2017 at 1:44 | answer | added | Ryan | timeline score: 1 | |
| Nov 19, 2017 at 0:59 | comment | added | Ryan | Using the main method thread to run the entire program produces the same results. After re-structuring the way the frame is setup I found that calling the JPanel class method paintComponent() rendered the image to the screen with 100% success until attempting to call 'frame.request(true);' in the Main class constructor. Input stopped working, and after fixing input the rendering chance has been reduced to ~70%. It seems the amount of threads present (including the Swing thread used during the uses of the repaint() and paintComponent() methods) is causing random encapsulation & focus errors. | |
| Nov 18, 2017 at 21:15 | comment | added | Ryan1729 | This is just a guess, but it seems like since the thread doesn’t create the screen and the frame, instead getting passed them from the main thread, the accesses to them might not be thread-safe/atomic, occasionally causing problems but sometimes working by chance. I assume you don’t need to access the screen and frame from the main thread anyway, so keeping them entirely on one thread would be better encapsulation. | |
| Nov 18, 2017 at 19:57 | history | asked | Ryan | CC BY-SA 3.0 |