Just a dumb question: how are you compiling? I.e. what is the command line you are using?

Update where is the risk: in case of malfunctioning you'll always be able to rollback to previous version.

Quote:

Selling a source license to someone is very different than releasing them in the public domain. Also another solution would be to have someone doing the update job for them without opening their sources. Some kind of subcontracting.

Using my Wacom driver (from OS4Depot most, if not all, USB Wacom tablets should now work under AmigaOS 4.1.

@All

The first public version of my Wacom driver is now out on OS4Depot. This version already supports sending tools information in the tablet event, interested application developper should look at the readme for more information on how they can detect it.

I've had to do something similar in one of my project (Wacom USB driver). In fact I used the functions you are referring to. This is not really mandatory if you only want to show the gui and you know the commodity id (just try to register the same commodity name and the previous commodity should show up). Else (you need to send more than just show, or you don't know the commodity id) you have no other choice than going that route and use these 3 functions.

Note that application.library can answer your need on that point. If you are not really writing a commodity (i.e. not tweaking with the user input) I would recommand switching to application.library.

Some tablets can have several styli (with different pressure, width etc.). Some supports wireless mouse too. And more commonly most styli have a "rubber" end at the nib opposite end.

My driver can identify this and can send this information in the tablet even using a new tag... So user application interested in this information can distinguish between all of them.

I'm finishing the driver preferences saving/loading part the I'll release the first public version. Due to personal reasons I can't work on it this week, but I have high hopes that I'll be able to work on it this week-end and probably at the beginning of next week I'll be able to release it.
Currently the remaining work required to reckon it really finished (feature wise) is adding possibility to configure non-mouse related function to tablet buttons (running exe, launching scripts, adding qualifiers, etc.). First I wanted this to be present in the first public version but real-life took over and I prefer releasing one version now and another later.

EDIT:
@328gts
Wacom tablets identify themselves as HID devices by default, which means that even without any driver you would be able to use it as if it were a mouse. However with a proper driver (like the one I'm working on) you'll be able to use pressure control, and use all buttons on the tablet and the stylus. If one day AmigaOS4 supports multi-tools my driver will be able to send this information too.

@freddix

As you have been answered on AmigaWorld FileInfoBlock is deprecated since DOS.library v51.104. Instead you *must* use ExamineObject() which will give you access to a struct ExamineData which contains almost the same data as FileInfoBlock plus some other in a 64 bits compatible way.

For your SystemTags() sample I think Ami603 as answered you in the same thread. Is this enough?

Sorry for the off topic.

@Thomas

Thomas, did you ever considered joining the official wiki effort for documenting AmigaOS (see AmigaOS wiki)? Your knowledge, your experience and your almost endless samples may really help improving our OS documentation. All those years each time I saw you giving advice or sample it was exactly answering the problem.

It depends from where you are trying to do that.
IIRC from an AmigaGuide document you can link to another using hyperlink and there you can specify the node to open, I can't check right now but I think it's something like
"mydoc.guide@mynode" but this need check (maybe it's a slash but it seems suspect to me because of possible confusion with the path separator).

Quote:

My guess would be that in case the stack cookie can not be interpreted it would stay at the configured system default value.

I was just emphasizing that unless you are using recursion the maximum stack usage can be calculated. All other method is just an approximation based on observation of a run. The result may or may not be accurate and more importantly may not be enough.

I don't know for sure but I doubt DOS will evaluate the cookie stack string and do the calculus.
Maybe you can use preprocessor stringification operator.

EDIT: oh and for #1 you can calculate by yourself the maximum stack size a program will take. All other methods will be the *observed* maximum on a given session using a given set of data, which might or might not be the real theoretical maximum.

@Mrodfr

Obviously a "Net up" tablet isn't a "Wacom" tablet, so my Wacom driver won't work with your tablet, sorry. Also I can't find anywhere information about your tablet, does it work under Linux? If yes do you know which driver is used?

@Andy

My driver already generates tilt information for supporting tablets (IIRC it's only Intuos). But it's untested yet because no one with such a tablet contacted me (I only found Seblam but it's very hard to contact and does not seems to answer emails either).

And here in France you can find used Wacom tablets for less than 20 euros (for example my Wacom Bamboo (old one) cost me 15 euros with original box and complete content).
Of course Intuos are a bit more expensive (even used) but you can find one starting from 100 euros here. I even saw a Cintiq 12" for 550 euros.

@broadblues

Yep that's true, but we don't know, maybe we still have some gfx professional among us...
Yes they have a cost, but for a professional tool that's not so high (it's not more than a high end Gibson for example ;)

Thank you, do you have any Wacom tablet yourself ?

Hi writing an USB Wacom tablet driver and as such I'm looking for testers.
Currently it was successfully tested on:
- Bamboo MTE-450A
- Graphire ET-405-U
- Volito FT-405-U
- Bamboo Fun CTE-450
- Bamboo One CTF-430

I'm looking for other tablets, if you are interested contact me by email with your product name and model number (as above) if you can extract your USB product ID from USB.log if would be even better).

EDIT: updated list of successfully tested tablets, still looking for Intuos and Cintiq...

@Hans

Quote:

Yes that's true and already some work has been done to improve that (dynamic tabs, editor gadget, etc.) but the road will be long.

Quote:

Yes I agree and it also probably has a great part of personnal taste. Anyway let's stop this here.

@kas1e

wxWidget was an amigabounty project so it's normal sources return to amigabounty team until someone else tries to look at it.

@Hans

yes you are right wxWidget *aims* at being a thin wrapper toward native GUI system. But fact is our GUI system is behind state of the art current GUI systems and only slowly catching up (ribbon? draggable toolbars? dockable windows? etc.) As a consequence you'll have no other choice than keeping the "universal" implementation (or write a not so thin wrapper trying to fill the defiencies), unless you are improving the native GUI system at the same time (which I can't do because of lacking inner knowkledge on Reaction).

Moreover wxWidget source code really feels its previous name (wxWindows) and it really mimic Win32/MFC API.