Version 1.2.2

WON'T WORK FOR ME AT ALL
----------------------------
* Do you have passwords set on your database? Unfortunately, I have no way to make the tool pass these to the psql command because of how that tool is implemented. While doing SQL editing, you'll have to remove passwords from your database. However, I suggest that you restrict it only to local access (127.0.0.1 address) and not outside access, to block bad guys. Another technique is that you can create a DBA user with an unguessable name like 'Uy4gftr' to limit access a little better. Would I like to change this? You bet I would! If you know a hack to get around this psql obstacle, let me know! :) Otherwise, I'm going to have to wait on the makers of the psql command to consider a way to not prompt for the password, but pass it at command line.

* Read the pgst.py file in the ~/apps/pgst directory. You'll find out lots of things about how this works, passing code to command-line for processing. You may, for instance, find out that I'm trying to call a GNU command line tool that you don't particularly have in your Linux build, so you may need to download that. (I used standard RH9 tools to make the application, by the way.)

PRINTING QUIRKS
--------------------
I am aware that printing is not up to par. It sort of works as of this release, but I've had reports of it printing the results for the wrong tab and other quirks. In the end I am looking for advice on how YOU would think this printing could be handled best, and if you have code samples, that's even better for me. Still, however, I am shooting for POLaR programming here (Path Of Least Resistance), meaning the least amount of code to get the job done effectively, and any of use of standard GNU printing and formatting tools to "cheat" is fair-game with me.

CAN'T PRINT SOME RESULTS
----------------------------
FIXED problem with non-UTF8 characters not printing to GTK TextView control. Now we display a dialog box about the error when this occurs.

SHORTCUT WON'T WORK
------------------------
FIXED problem where the GNOME shortcut path was completely incorrect in 1.1.0.

CUT AND COPY PROBLEM
------------------------
FIXED problem where cut and copy would fail to work on selected text in some cases.

POPDOWN LISTBOXES WON'T WORK PROPERLY, COSMETICALLY
----------------------------------------------------
FIXED problem where, of the type of popdown listboxes that needed to dynamically download lists from various databases, tables, and columns, I could not get the popdown to download the list and leave it on the screen once the list was downloaded. Instead, it would have just downloaded it and reset the state of the popdown. Therefore, I had to add a top row that said, "<item> List Downloaded" so as not to confuse the user. Well, by accident I stumbled on the fact that if I use grab_focus on another field during the click event of the popdown, it would leave the list open. Therefore I did not need to add the "<item> List Downloaded" row anymore.

FIELD EDITOR - KEY VALUE POPDOWN NOT THERE
---------------------------------------------
It used to be that the field editor required you to type in a unique key value and guess what that might be. I eventually realized that this was silly and, instead, made it automatically get those values and create a popdown listbox out of it.

INSTALL HARD-CODED
---------------------
FIXED problem where the install was only hard-coded. Now it prompts for where to install the application. You also don't need to press CTRL+C to abort the install.

FIELD EDITOR - SPACES REMOVED FROM KEY VALUE
-----------------------------------------------
FIXED problem where the key value field in field editor was removing spaces because of the 'tr' command. Now use a different technique for that field so that spaces are working in field values.

