GASP crashes after begin_graphics()
Bug #162089 reported by
Heath Matlock
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GASP Core |
New
|
High
|
Unassigned |
Bug Description
Using Windows and after importing GASP and all its sub-modules by typing
from gasp import *
and then typing
begin_graphics()
a blank window pops up, but doesn't display anything. After awhile, it's recognized as not
responding. Not sure if it would help or not, I tried
from pygame import *
and still got the same results. Did the exact same procedures with the latest nightly build a few seconds ago.
Changed in gasp-code: | |
importance: | Undecided → High |
milestone: | none → 0.2 |
Changed in gasp-code: | |
status: | Incomplete → Invalid |
Changed in gasp-core: | |
status: | Invalid → New |
To post a comment you must log in.
Two clarifications, pygame was imported before gasp, and the results for the nightly build were the same as previously stated.