Quote: "Do you know whether the special characters and things from Visual Basic are the same as the ones in this plugin? "
It depends if VB uses perl, posix, or (quite likely) an MS variant.
Special meta-characters like "\w" are
not POSIX compatible characters, however stuff like [:alpha
is. IIRC.
Quote: "adr, good job."
The annoying part of development was knowing how much easier this would be in managed c or c#. I'm glad I persisted though - very satisfying. I could go even further, and try to make the plugin smaller by not using the vector STL class. I don't fancy dynamic arrays of strings though. I'm seeing why plugin development is so popular around here; it's DBP-related, but with a real language.
Quote: "sorry I never added the input console to the dbp_netlib - we did talk about that, didnt we?"
Yeah - I've forgotten the functionality we discussed to be honest ...
Originally, it was just a quake-console input type thing. It would ease parsing out the command and parameters to the command. With this plugin and a bit of DBPro work, that's working out quite nicely.
I think one of the bigger ideas for the plugin is that you could "register" variables with the plugin from DBPro. Essentially, the variables are stored in the plugin under huge associative arrays and DBPro supports a
netlib get float/string/int type function which reads it back in.
The cool part is that the plugin has a nice interface for altering variables and therefore, if DBPro is retrieving the values from the plugin, the behaviour of your app is altered immediately (in theory).
D'you know, I'm tempted to have a go at that... Maybe the interface could be "in-engine" ... BlueGUI? Or even a text console... hmm. ideas.
[center]
iv tryed everything!!!!!!!!!! could u please just add The gun and shooting Code thats All!!!!!!!!!