Yes, quite seriously, my lack
of programming is very likely the cause of any errors. It is essentially a minimal packet request and display from the tablet driver using wintab functions. I am not a programmer, which is why I use Construct... however, I can say the issue of 1024 being hardset on my part only pertains to the height scaling of the pretty orange bar. It may, however, be possible that wintab is unable to create a streaming context with your tablet driver because it, in my minimal test, has not been set up to a) gather information about your tablet and b) configure itself properly in respects to your tablet's capabilities.
This configuration and info gathering I simply have not yet looked into setting up because I don't know what I'm doing in the first place. Rather, I don't know what the code is doing, and therefore do not know how to organize it - it would take a bit of trial and error, be a learning process on my part - and I have been busy with other things. It's possible that 1024-level Wacom tablet compatibility is just the default, unconfigured mode it runs in. I would not yet believe wintab is Wacom-only: isn't this the library GIMP uses? I don't know for sure.
Sorry to have not stayed caught up on this thread. Here's all I had done. Much of the python scripting within the cap is salvaged nigh verbatim from the first in this list of resources. Perhaps you can try running his test python game to see if it functions with your tablet - there are many measures he has included that I first attempted to include, but eventually cut due to not knowing how to structure it in Construct. Evidence of this is in the vestigial var prevpressure, which is defined but never used. I forgot to delete it, haha. [size=85:i84kat9q](Early blind attempt that would cause Construct to crash on the condition of event six
.)[/size:i84kat9q]Scripts and .cap:http://dl.dropbox.com/u/398143/Files/wi ... essure.zip
Merge the contained Data folder with the one in your Construct install directory. The .cap should be able to access the wintab libraries from there; you need only have Python 26 installed.Information resources used:http://www.akeric.com/blog/?p=777http://cgkit.sourceforge.net/doc2/wintab.htmlhttp://www.wacomeng.com/devsupport/pc.html
In the last link there, there are samples with source code. They seem like they'd be useful for studying the structure of wintab function usage, I have simply not yet gotten into it.
[quote:i84kat9q]I get an error stating line 12 stating that Wintab couldn't find context followed by recurring errors about line 1 and context not being open.[/quote:i84kat9q]
This could be several things. Perhaps wintab cannot find the context it accesses in your tablet drivers... or perhaps the first python scripting module simply cannot find the definition of the context class __init__.py defines. Either would cause the subsequent every-tick module to whine about the context not being open, because it was not opened in the first script module.
In regards to line 12, there is no line 12; I don't know why, but Construct seems to count its script lines from a different angle than they are presented in the script editor, and as such they are often misleading. I checked the scripts and such but they all have open licensing comments through the first twenty or so lines. A better look at what exactly the error pop-up is saying, if it's saying anything more, such as whether it's complaining about an external script, or what, would make it easier to trace.
As for error-trapping, I don't know, I have never really had any problem with forcing a process to end. The errors that do show are generally informative enough.