AutoHotkey Community

FaxTool 0.20

Hey everybody.
I was looking for some free TIFF splitter and joiner, to use with the faxes I send and receive.
Since I could only find ones that require payment, or ones that only do part of the job (usually with a lot of GUI...), I wrote this little script to do this for free and with ease.


FaxTool lets you split and join TIFF / PDF files by simply dragging them onto the interface.

In fact, this is just an AHK GUI wrapper.
The actual conversion is done through LibTIFF and PDFTK executables which are FileInstalled into this script.

Source code and downloadable compiled version can be found here.

If someone finds it useful, enjoy.

_________________
Sector-Seven - Freeware tools built with AutoHotkey

Version 0.11 - now supporting splitting and merging of PDF files as well.

_________________
Sector-Seven - Freeware tools built with AutoHotkey

Very nice, something anyone would be able to incorporate into their routine, maybe post scanning a few docs? Thanks

simple, useful, and clean... nice work

i tried it at work today, we get a lot of groups of single page pdf's (blueprints) to quote and with a simple drag n drop this was already very useful for me, so thanks

one quick recommendation i have is to use the existing file name, and append the page number to it (ie ThisDoc.pdf becomes ThisDoc-pg1.pdf, ThisDoc-pg2.pdf, etc) so if more than one file is split in the same directory...

thanks
- joel

Thanks joel,

About the filename, I will check if the conversion executables have a command argument to set the output name, or maybe I will do a post conversion rename.

_________________
Sector-Seven - Freeware tools built with AutoHotkey

Great Thank's Icarus.,You simplified my life!

(words for french recherche
Petit programme pour Regrouper des .Pdf en un seul. Ou pour couper un Pdf en plusieurs)

_________________
with ahk, all is different!...<img>

A very helpfull little tool. Thanks for sharing it.

_________________
Greetings
Rog

Released version 0.20

Output filenames will be based on the input filename:
Split of SomeDoc.pdf will produce SomeDoc_1.pdf, SomeDoc2.pdf
Join of SomeDoc_1.pdf and SomeDoc_2.pdf will produce SomeDoc_merged.pdf

_________________
Sector-Seven - Freeware tools built with AutoHotkey

Hey Icarus,

I was wondering what kind of (if any) feedback you get regarding the temporary exe's.
For instance, how do antivirus apps behave?
Have you had any problems with false postives or any blocking of the extracts?
What about UAC on non XP os's?

I'm planning on distributing some applications that also use 3rd party apps as processors and was worried about his exact problem.

Thanks in advance for any info.

_________________
paradigm.shift:=(•_•)┌П┐RTFM||^.*∞

Good questions.

In regards to the separate EXE files, I did not get any negative feedback.

In regards to antivirus false positive - I am getting quite a few of these, with almost all my compiled AHK scripts.
Every now and then, some antivirus (usually AVG...) decides that my AHK scripts are "suspected" or "trojan".
Recompiling with a newer AHK version solves it usually.

In regards to UAC - I am having some difficulties with it, and getting some complaints.
All my scripts are writing to an INI file (for settings), and some vista users complain that the settings are not saved - I am blaming UAC.

Is there anything that can be done with the UAC issues (other than disabling it altogether?).

_________________
Sector-Seven - Freeware tools built with AutoHotkey

1st off I want to thank you for such a speedy reply.
Its nice to have someone to talk to about this (my wife hates it when I try to explain this stuff to her ).


With regards to either an INI or text file for prefs, I recently started an app that has to recall last user info.
I opted to use the registry rather than an INI for reason that UAC can block it and or there would be no need for an external file.
There was absolutely no UAC alerts on either Win7 or Vista machines. I did get some intermittent recall falts where Vista would not fully recall reg info, but this only occurred when there were, say, syntax errors in the underlying AHK script.
Perhaps this could be a good workaround for you??


I fully understand the issue of false positives due to upx compression.

The things I worry about when using 3rd party apps packaged into a central exe are:

- false interpretation as a virus/malware delivery app.
- licensing (re-distribution).
- future compatibility of the 3rd party applications.
- 3rd party apps triggering the UAC (IMPORTANT!)
- getting a bad reputation from users or the 'programming community' for use of these apps.

I know I could learn more about WinAPI that would probably give me tonnes of practical workarounds.
The problem I'm finding is the learning curve is extremely steep.
It almost makes more sense to me to (finish) learning C++.
Then I could just create my own single exe or dll. For rapid development this sucks though.

I don't mean to whine, but seeing as you have software distributed on the net, your opinion of all this is greatly appreciated .

_________________
paradigm.shift:=(•_•)┌П┐RTFM||^.*∞

I hear you...



I want mobility and transparency.
When everything is in the scripts folder, including settings, its easy to understand (for users) and easy to take on a USB drive.



False positive will always be an issue probably because of UPX, but it happens to me about two times a year that someone points out that some antivirus software thinks its a virus.

In regards to licensing, yes, need to make sure redistribution is allowed.



I agree. The thing is I hate the bloated development environment.
Comparing the super lightweight notepad2 with some version of the visual studio keeps me in the comfort zone of rapid AHK development.



any time

_________________
Sector-Seven - Freeware tools built with AutoHotkey

I see.
Portability (and multi file support) is also something that I've been looking into of late.
I'm wondering if writing to the registry will ever add an extra UAC layer. Its such a cumbersome alert.
I'd rather my users have to deal with it at a minimum!
Funny enough I've found some lower level functions that ONLY allow for files to be read from the script dir so it looks like this is going to be the norm for me anyway (for now) .

I was referring to the motherload WinAPI . On a serious note, I hear that C++Ox is going to be very 'straight forward' way to develop in the near future. More here: http://en.wikipedia.org/wiki/C%2B%2B0x

Oh before I forget, just as a test, I wanted to see if 3rd party command line executables could be run even if the extensions were changed (to avoid the obvious usage).
Low and behold low level functions and comspec all excepted the exe's as long as the extension was substituted (and not blank).
Now this has me wondering, could the system see this as a potential 'hideaway' for a threat?

Looks like its a job for the beta testers !

_________________
paradigm.shift:=(•_•)┌П┐RTFM||^.*∞

To be honest, I never took the time to fully understand UAC - I am guessing there should be a normal way for an application to write to its own folder... no?

In any case, when I get complaints from vista users that do not want to disable UAC, I simply tell them to install the program in a folder different than program files - and it usually eliminates the problem.

A less than ideal solution, to a less than ideal OS...

_________________
Sector-Seven - Freeware tools built with AutoHotkey

A very good idea and something I will take into consideration in the future !

_________________
paradigm.shift:=(•_•)┌П┐RTFM||^.*∞