FAQ: how to control the size of the image that is getting generated on Linux.

When you use html2image Linux on Linux OS, you can convert any URL into image.

But some times, you may need more advanced image processing features such as controlling the size of the image.

The solution is simple: you can use tools like ImageMagick or perl to easily resize the image to your size requirements after converting html to image with html2image linux.

The snap and processing tools can be glued together by linux shell script or any other scripting language like perl, php etc. 

 

FAQ: Does AAR support simultaneous recording from different sources

Yes, our Audio Record Component  supports recording multiple sources on the same PC.

Suppose you have more than one sound card installed, in order to record on the two cards simultaneously,

1. Create multiple audio record object

2. Set the correct device index and device line index.

3. Start recording of all the objects

Each record object can record its source perfectly

 

Porting IDL to win64

I found a good guide article on MSDN today on this topic:

USER and GDI handles are sign extended 32b values To facilitate the porting, a decision has been made that these system handles should stay as 32b values, sign extended to 64b on the 64b platform. That is, the individual handle types are still based on the HANDLE type, which maps to void *, and so the size of the handle is the size of the pointer, i.e. 4 bytes on 32b and 8 bytes on 64b. However, the actual value of the handle on the 64b platform, (i.e. the meaningful bits), fits within the lower 32b, while the upper bits just carry the sign. This should make it easy to port the majority of the application code. Handling of the special values, like –1, should be fairly transparent. It also should agree nicely with all the cases where the handles had been remoted with the help of the IDL definitions from the public file wtypes.idl. However, care needs to be taken when remoting the handles was done via a DWORD, as the upper long should be properly sign extended on the 64b side. The app should use HandleToLong() and LongToHandle() macros (inline functions) to do the casting right. So, in general we can have the following situations: A handle like HWND, HMENU, HPALETTE, HBITMAP etc was sent as its own type (that is specified with HMENU, etc. as the type of the argument) – do nothing, ole32.dll code handles situation as appropriate A handle was sent as a DWORD – you can: leave it as such and cast the wire value to handle using LongToHandle() change the argument to long or LONG_PTR; this is possible in some cases only, When designing a new interface, in order of preference: use the types themselves, use context handles or use a LONG64 argument to hack through. Going back to specifics of porting the legacy code, the following system handles fall into the nice 32b compatible category. The USER handles: HWND, HMENU, HICON, HCURSOR, HDWP, HHOOK, HACCEL, HWINSTA, HDESK, HKL, HMONITOR, HWINEVENTHOOK. The GDI handles: HBITMAP, HPALETTE, HMETAFILE, HENHMETAFILE, HMETAFILEPICT, HBRUSH, HFONT, HDC, HRGN .

Bug tracking system

Trac is a web-based software project management and bug/issue tracking system emphasizing ease of use and low ceremony. It provides an integrated Wiki, an interface to version control systems, and a number convenient ways to stay on top of events and changes within a project.

Trac is distributed under the modified BSD License. The complete text of the license can be found online as well as in the COPYING file included in the distribution.

 Please visit the Trac open source project at http://trac.edgewall.org/.

Christmas is coming

The holiday season is coming now.

Wish you all have good holiday.

We will give 15% discount on all software products in the holiday season.  The more you buy, the more discount we give.

Email us for the products you interest. We will send you discount links

Action quickly now! :)

 

Fill PDF form with PDF stamper ActiveX

We add a new feature to PDFStamper ActiveX. Now it supports Fill forms in PDF file.

The syntax for filling form is easy. First add all the form field name and correspondent value (strings),

then apply the field values to an input pdf file, the filled forms will be stored as a new output pdf file.

The example is below:

Dim pdf
Set pdf = CreateObject(“PDFStamp.PDFStamper.1″)

pdf.SetCode “Your license code here”

pdf.AddFormField “name”, “your name”
pdf.AddFormField “address”, “your address”
pdf.AddFormField “postal_code”, “xyz”
pdf.AddFormField “email”, “xyz@hotmail.com

pdf.ApplyForm “..Form.pdf”, “Form_nonflat.pdf”, 0