But even with that approach, there will be situations (i.e. I have ideas for this, based on the notion of JIT de-compilation and re-compilation. To do libraries correctly I first need to find a new means of introducing Script Debugger’s debugging hacks into loaded code. There are other issues as well: Script Debugger’s UI is built around the we need to adopt an Xcode-like UI where a script is composed of many source documents.
#Script debugger returned error 29294 code#
Further, because Script Debugger uses its own OSA component, AppleScript interprets code saved with debugging enabled as something other than AppleScript and reports the errors you are seeing. As a result, Script Debugger is unable to introduce its debugging hacks where needed. These actions take place within AppleScript and beyond the reach of Script Debugger. The use of a custom OSA component facilitates debugging within other host applications (Mail, etc.).īut, as always, there is a problem when AppleScript loads code on the user’s behalf ( load script, use script, run script).
This is accomplished using Script Debugger’s own OSA component ( ~/Library/Components/Script ponent). Script Debugger’s exploits this single compilation unit model to introduce its debugging hooks at compile time. Sure, you could use the load script command and Script Debugger had its own library facilities, but most scripts were the result of a single compilation unit. Think of Script Debugger as a Porsche 911: a really bad idea executed very well.īack before the appearance of AppleScript Libraries, AppleScript scripts were monolithic. Everything Script Debugger offers is done by various forms of hacks. What follows is simply an explanation, not a defence of the current state of affairs.ĪppleScript provides a very limited API for developers, and absolutely nothing to facilitate debugging. Unfortunately, a solution was outside the scope of the Script Debugger 6.0 effort. _style(0, len(, this is a problem that I recognize. tText(ContadorA, log=False)įile “C:\Program Files\PsychoPy\lib\site-packages\psychopy\visual\text.py”, line 383, in setTextįile “C:\Program Files\PsychoPy\lib\site-packages\psychopy\tools\attributetools.py”, line 134, in setAttributeįile “C:\Program Files\PsychoPy\lib\site-packages\psychopy\tools\attributetools.py”, line 27, in setįile “C:\Program Files\PsychoPy\lib\site-packages\psychopy\visual\text.py”, line 374, in textįile “C:\Program Files\PsychoPy\lib\site-packages\psychopy\visual\text.py”, line 392, in _setTextShadersįile "C:\Program Files\PsychoPy\lib\site-packages\pyglet\text_ init.py", line 456, in init
KeyError: ((‘v2f/dynamic’, ‘t3f/dynamic’, ‘c4B/dynamic’), 7, False)ĭuring handling of the above exception, another exception occurred:įile “C:\Users\gabri\psychopy\PSAP_FINAL_lastrun.py”, line 714, in Creating a temporary one…įile “C:\Program Files\PsychoPy\lib\site-packages\pyglet\graphics_ init_.py”, line 452, in _get_domain Using actual sizeĢ.2605 WARNING Monitor specification not found. There’s no new variable introduced just before it stops, and making the experiment shorter keeps it from crashing, but I really need it running for 25 minutes.ġ5.0970 WARNING User requested fullscreen with size, but screen is actually. Unfortunately, the experiment stops just around 24 minutes. I have an experiment that its supposed to keep running trials for 25 minutes.
0 kommentar(er)
