Blog

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
With this setting you can specify which license to use.
 
 

Win32 api download pdf

Direct output to the same file each time or prompt for destination. Control if the printer should ask if you want to see the resulting PDF document.

Control settings and prompts programmatically. Setup can run unattended. Graphical user interface. Password protect PDF documents. Quality settings screen, printer, ebook, prepress. Set document properties. Print to PDF from almost all Windows applications. Current version: 9. All Features 13 Free Features Categories Tree. Avail of Advanced Save Settings Use advanced save settings to save files, strip paths from document names, add macros and run applications automatically after documents are printed.

Determine Paper Settings Adjust paper size, scaling, basic graphic resolution and layout options. Need more information? IDOK is the control identifier. IDOK is pre-defined so we don’t need to define it ourselves. The four numbers at the end are the left, top, width and height, all in dialog units.

This information should be purely academic, as you almost always use a resource editor to create dialogs, but knowing how to do it from text is sometimes necessary, expecially if you have no visual editor.

However it doesn’t hurt to give them an ID and your resource editor might do so automatically. Having added that to your. Don’t worry this is nothing new, it’s practicly the same as our main Window Procedure but not exactly.

With dialogs this is done automatically for you and will really screw things up if you do it. The second paramter is the value that is returned to whatever code called DialogBox. Enough chit-chat, lets create it Since we want the menu on our main window to create the dialog, we obviously want to put this code in the WndProc of our main window, not the dialog proc. Now I stored the return value from the call to DialogBox , this is just so you can observe the effects of pressing the two buttons, hitting Esc, Enter etc It also illustrates how to use the return value from a dialog box to check for success, failure, a users choice, or whatever other information you choose to send back to the caller from the Dialog Procedure.

AboutDlgProc is of course the dialog procedure to use to control the dialog. That’s it! A perticularly astute reader might eventually wonder, if DialogBox doesn’t return untill the dialog closes we can’t process messages while it’s up, so how does it work? Well the nifty thing about DialogBox is that it has it’s own message loop, so while the dialog is displayed, our message loop is out of the picture and the default loop is handled by windows. This loop also takes care of fun things like moving the keyboard focus from control to control when you press Tab.

Another effect of using DialogBox is that your main window is disabled untill the dialog is dismissed. Sometimes this is what we want, and sometimes it isn’t, such as when we want to use a dialog as a floating toolbar. In this case we want to be able to interact with both out dialog and our main window, and this will be the focus of the next section.

The difference is that while DialogBox implements it’s own message loop and does not return untill the dialog is closed, CreateDialog acts more like a window created with CreateWindowEx in that it returns immediately and depends on your message loop to pump the messages as it does for your main window.

This is termed Modeless, whereas DialogBox creates Modal dialogs. You can create the dialog resource just like you did for the last dialog example, you might also want to set the “Tool window” extended style to give it’s title bar the typical smaller caption of toolbars. We also want to declare a global variable to hold the window handle returned from CreateDialog so that we can use it later.

DialogBox didn’t return a handle to us since when DialogBox returns the window has been destroyed. Now we need a dialog procedure for our toolbar. One change is that we don’t call EndDialog for modeless dialogs, we can use DestroyWindow just like for regular windows. In this case I destroy the dialog when the main window is destroyed. In the main window’s WndProc Now when you run the program, you should be able to access both the dialog window, and main window at the same time.

If you’ve run the program at this point and tried tabbing between the two buttons, you have probably noticed it doesn’t work, neither does hitting Alt-P or Alt-O to activate the buttons. Why not? Whereas DialogBox implements it’s own message loop and handles these events by default, CreateDialog does not.

We can do it ourselves though, by calling IsDialogMessage in our message loop which will do the default processing for us. Is this case the message has already been handled so we don’t want to call TranslateMessage or DispatchMessage.

If the message is for another window we process as usual. And that is pretty much all there is to modeless dialogs! One issue that may arise is if you have more than one toolbar Well one possible solution is to have a list either an array, an STL std::list, or similar and loop through it in your message loop passing each handle to IsDialogMessage until the right one is found, and if none, do the regular processing.

This is a generic programming problem, not one that is Win32 related, and is left as an excersize to the reader. ControlsOne thing to remember about controls is that they are just windows. Like any other window they have a window procedure, a window class etc Anything you can do with a normal window you can do with a control. MessagesAs you may remember from our earlier discussion of the message loop, windows communicate using messages, you send them to get a control to do something, and when an event occurs on the control it will send you a notification message back.

The messages you send are widely varied between each control, and each control has it’s own set of messages. Once in a while the same message will be used for more than one kind of control, but in general they will only work on the control they are intended for.

A control is just a window after all. EditsOne of the most commonly used controls in the windows environment, the EDIT control, is used to allow the user to enter, modify, copy, etc Windows Notepad is little more than a plain old window with a big edit control inside it.

Retreiving the text from the control is easy as well, although slightly more work than setting it In order to do this, we first need to know how much memory to allocate. Now that we have the length, we can allocate some memory. Here I’ve added a check to see if there is any text to begin with, since most likely you don’t want to be working with an empty string Assuming that there is something there to work with, we call GlobalAlloc to allocate some memory.

It allocates some memory, initializes it’s contents to 0 and returns a pointer to that memory. There are different flags you can pass as the first paramter to make it behave differently for different purposes, but this is the only way I will be using it in this tutorial. Note that I added 1 to the length in two places, what’s up with that? This means that if we were to allocate a string without adding 1, the text would fit, but the null terminator would overflow the memory block, possibly corrupting other data, causing an access violation, or any number of other bad things.

You must be careful when dealing with string sizes in windows, some APIs and messages expect text lengths to include the null and others don’t, always read the docs thoroughly. If I lost you talking about null terminators, please refer to a basic C book or tutorial which discusses strings. Finally we can call GetDlgItemText to retrieve the contents of the control into the memory buffer that we’ve just allocated.

The return value, which we ignored here, is the number of characters copied, NOT including the null terminator To accomplish this, we simply call GlobalFree and pass in our pointer.

Edits with NumbersEntering text is all well and fine, but what if you want the user to enter in a number? This is a pretty common task, and fortunately there is an API to make this simpler, which takes care of all the memory allocation, as well as converting the string to an integer value.

GetDlgItemInt works much like GetDlgItemText , except that instead of copying the string to a buffer, it converts it internally into an integer and returns the value to you. The third parameter is optional, and takes a pointer to a BOOL. Since the function returns 0 on failure, there is no way to tell just from that whether or not the function failed or the user just entered 0. If you are fine with a value of 0 in the event of an error, then feel free to ignore this parameter.

This is very handy if you only want positive integers, otherwise it’s not much good, since you can’t enter any other characters, including – minus. List BoxesAnother handy control is the list box.

This is the last standard control that I’m going to cover for now, cause frankly they aren’t that interesting, and if you aren’t bored yet well, I am :. Adding ItemsThe first thing you’ll want to do with a listbox is add items to it. This message returns the index of the new item either way, and we can use this to perform other tasks on the item, such as associating some data with it.

Usually this will be things like a pointer to a struct containing more information, or maybe an ID that you will use to identify the item, it’s up to you. NotificationsThe whole purpose of listboxes is to allow the user to select things from a list. Now sometimes we don’t care when exactly they do this, for example with our Remove button, we don’t need to know when the selection changes right away, we just check when the user activates the button.

However, sometimes you want to be able to do something right away, perhaps display different or updated information based on what items are selected. In order to do this we need to handle the notification messages that the listbox passes to us. Getting Data from the ListBoxNow that we know the selection has changed, or at the request of the user, we need to get the selection from the listbox and do something useful with it. In this example I’ve used a multiselection list box, so getting the list of selected items is a little trickier.

First we need to get the number of selected items, so that we can allocate a buffer to save the indexes in. Do stuff with indexes GlobalFree buf ; In this example, buf[0] is the first index, and so on up to buf[count – 1].

One of the things you would likely want to do with this list of indexes, is retreive the data associated with each item, and do some processing with it.

This is just as simple as setting the data was originally, we just send another message. StaticsLike buttons, static controls are largely trivial, but for the sake or being complete I include them here.

Static controls are usually just that, static, meaning they don’t change or really do anything else very special, they’re largely for displaying text to the user. In the example code, I use one to display the data of the item selected in the list box, assuming one and only one is selected.

Changing ColoursIn general, the only reason you’d want to do this is to simulate an link on a dialog box or some similar task, because otherwise you’re probably just making your program ugly and hard on the eyes if you go adding a bunch of colors to the dialogs, but that doesn’t stop people from doing it, and there are actually a few valid reasons, so here you go : Windows sends a variety of messages related to colours to your dialog procedure, and by handling these messages you can change what colour certain things are displayed in.

Fix for size of background PDF when running as a shared network printer. User interface is now DPI aware. Fonts look nicer in different screen resolutions. Fix for running as a shared printer. Some print jobs looked different when coming from a shared printer. GUITimeout setting -1 problem fixed by keeping the document collector running until the GUI has finished processing the job.

Support for XPS based printer drivers as an alternative to Postscript. This provides better Unicode support. Handles error where a configuration with an encrypted password is moved to another machine. Trial message is now a link for more information. Unicode font support brought back to previous level. New macro tag added. Text extraction was improved. FIPS compliance detection added for new operating systems. GUITimeout defaults to 0 for better performance on multi user systems.

Shows license type on about page. Shows printer window in task bar. New Merge function in API that supports font embedding. Security updates. Enhanced special character support in PDF passwords. New setting ‘textfilename’ to save the content of the print job as text.

New setting ‘textformat’ controls if the text file is formatted as Unicode or UTF8. Fix for encryption of PDF versions lower than 1. Default GUI timeout was changed from 0 to 10 minutes for a better merging experience. Fix for commercial distiller PPD to enhance compatibility. Fix for job names on printer queue when sending output to another printer.

Installs on Windows Server Preview 4. Ignore empty registry settings. False positive virus detection removed. Support for commercial distiller on file systems without short names. Fixes file time stamp for attached files. Print to printer after output is created.

AllowExecute setting added to the registry to improve security. Commercial distiller now uses Flate image compression by default. PrinterName context variable added for VBS macros. Fixes problem with save as dialog selection being lost. Fix for Korean Unicode license decoding. NET 2. Remember last used option set with support for hidden dialogs. Fixes for systems without support for 8.

Escaping of characters fixed for job specific runonce file naming. Improved support for file names with regional characters in the Merge function.

Updated translations: Swedish, Slovenian, Urdu New hideoptiontabs setting to control which tabs are visible in the options dialog. Fix for hiding run action error dialog in silent mode.

Improvements for non-interactive users. New installer switch: PostScriptLanguageLevel to control the language level of the driver. New installer switch: PostScriptOutputOption to control the output options of the driver. New installer switch: DPI to control the default resolution of the driver.

New installer switch: AdvancedFeatures to enable or disable the advanced features of the PostScript driver. Advanced features of Postscript driver were disabled to fix left to right LTR printing issues. Registration of msscript. Now uses ps2write device for PostScript generation with Ghostscript. More paper sizes added. Translation updates: Polish, Slovak. Fixes installation error: Operation could not be completed error 0x The specified port is unknown.

AES bit encryption is now supported with the commercial distiller. Support for macro in watermark text. Improved port monitor reports errors to the event log. Fixed copying sample configuration files for custom printer names. New LicenseData setting to hold a base64 encoded license string.

New IgnoreCopies setting to make only one copy of a document in the PDF instead of the specified number in the print job. New FastTrack setting for fast image creation. Many features are ignored in fast track mode. Administrators can now use the printer on a remote connection without a professional license. Supports hard coded license levels in redistribution builds. Fix for temporary paths with Unicode characters. Fix for systems with multiple copies of the same font.

Fix for not remembering the last output device. Commercial distiller uses standard encoded fonts. Install option to override default TrueTypeDownload setting. Performance tuning through GSGarbageCollection setting. Option dialog now supports running programs on success and error. Option dialog now supports running program after processing a print job. New setting to control confirmations of folder creation. Advanced option dialog with buttons to edit global.

New options dialog tabs for file upload, running programs, and signing with digital certificates. Supported Ghostscript version is now 9. Improved Unicode support.

Belarusian translation added. New experimental PdfUtil. PrintPdf function in API. More Unicode stuff. One MSI package for both silent and non-silent installation. Does not set the installed printer as default unless no default printer was selected by the user. Additional registry cleanup in uninstaller. Cleanup of failed print jobs.

Support Windows was discontinued. Image compression is turned on by default. Image compression setting can be changed from the user interface. Digitally sign PDF files using certificates in the certificate store. Improved uninstall routine for cleaner uninstall. GUI encrypts owner and user passwords in configuration files. Fixes loading of option sets with different device settings.