Updates:
- Fixed some parts of the GUI wizard. Also fixed rlWriteVarName mis-behavior.
- Added new parameters to rlJoinIt function, allowing you to set the path to where the target file will be created, and allows you to set a switch for a function to be able to delete the source split files or not.

Nice work. Some function are currently at hand in other plugins.Autoit provide some similar commands, but of cource a external DLL is necessary.I wish I would have had the time to make such a nice HLP as you did.A sample pub could be also usefull.

@HPWwell... yes your right, there are already available plugins that have this functions. But, this is just the beginning and I think the basic functions must always be included (right?).

About the sample pub? i don't know... but i'll try, i know i already tested them. But thinking of making a sample pub that includes all rlFunctions can be quite frustrating (hehehe) coz they're too many. Well probably on the next release it'll have a sample pub.

> Why? When you test them you have a sample. So what is needed more? Ok, a little polish may be needed.

Yes I do have the pub which i used to test each functions, however as you've said, it really needs a major polishment, coz i put all functions in a single page, and they overlapped each others. That's why i would never send the test pub i made, coz none will be able to understand it, except of-course me (lolz). Which means I have to make a simpler and organized pub for the plug-in. (that's why it seems kind a frustrating, lolz). Anyway, on the next release, it'll probably have.

> Another point. I tried upx 1.25 on your plugin and now it is 51 KB instead of 172 KB. Maybe you want to get it a bit smaller.

Yes i know UPX, but I think there's no need to compress the plug-in, since i can distribute it in zip or rar. Also (correct me if im wrong) NeoBook has the capability to compress files internally (including plug-ins).

@SpiritHorseNOOT> keep up the good work reynold

huh? what do you mean? it ain't really helpful. Am I that perfect to you? (lol).

Quote: from SpiritHorseNOOT on 2:34 am on July 27, 2004no i didn't say you was perfect

You have some good functions that other plugins don't have to my knowledge ...... for example rlGetAllAppHandle

this gets the handles of everything just about that is visiable on the windows desktop including the sub handles of applications

thank you very much and yes... i too agree(so far) with that. I'm still researching/studying some Win32API functions that'll be included in rlFunctions. However, lots of WINAPI functions aren't really easy to implement in neobook. So my head-aches (lol)

Just a tip: all the windows (not Graphics Objects) got a handle. Even a simple button or a edit box got a handle (well, a button or a combobox or a edit box are windows and have handles, like applications). Getting all the handles in the same time can be a memory consuming task.

Quote: from Alberto Meyer on 7:08 am on July 27, 2004Just a tip: all the windows (not Graphics Objects) got a handle. Even a simple button or a edit box got a handle (well, a button or a combobox or a edit box are windows and have handles, like applications). Getting all the handles in the same time can be a memory consuming task.

Thank you very much for tip

I will sure take consideration of that. And yes it's true that almost everything running in Win32 environment contains handles, coz in Win32 they're all just individual window with individual handles. Which is a good feature of windows, coz you can control objects(like textbox,buttons,etc), you can get info, pass info, show/hide the object, or even remove objects (im not sure about adding objects into external applications).Anyway... thanks!

Quote: from SpiritHorseNOOT on 5:39 am on Aug. 11, 2004could you possiblably add the ability to get text from a window/class

Yes, definitely! the rlGetAppTitle is one sample, it retrieves the Application Title of a window based from its handle (hWnd) and/or classname.

Also since all objects in a window application are actually created under CreateWindow() and/or CreateWindowEx() their text/values,captions, and classnames can be retrieved.

The key to this is the Win32API GetWindow() function.

... huh? oh! i get it. You mean a function to retrieve parameters from any windows and/or objects in an application? Well... yes, Nice idea! but... It can be quite difficult implementing it without side-effects of consumption of memory resource being too large. Anyway, i'll put it in my TODO memo just if i forgot(LOL).