Click here to Skip to main content
15,890,741 members
Articles / Desktop Programming / MFC

ToDoList 8.2 - An Effective and Flexible Way to Keep on Top of Your Tasks

Rate me:
Please Sign up or sign in to vote.
4.85/5 (2,418 votes)
17 Sep 2023Eclipse12 min read 59.1M   441.3K   3.6K   32.8K
A hierarchical task manager with native XML support for custom reporting

Downloads


3rd Party

Note: Please contact the respective authors directly with comments and questions

todolist2/CP_screenshot2.png

Latest Update (8.2 Feature Release)

  • Added 'Markdown' comments
  • Added highlighting of 'Circular Dependencies'
  • Added 'Calculations' to 'Custom Attributes'
  • Added 'Custom Date' attributes to 'Week Planner'
  • Added 'Custom Date' attributes to 'Calendar'
  • Added 'Drag and Drop' from 'Explorer' to 'Spreadsheet' comments
  • Added dedicated toolbar button for creating 'ToDoLIst UDTs'
  • Added 'Recurrence' options to 'Filter Bar'
  • Added '-mp' command line switch to use first decryption password as a 'Master Password'
  • Added toolbar button to 'Find Tasks' dialog to allow closing when docked
  • Added 'Calendar' preferences to show 'Week Number' in cell header
  • Added 'Straight Line Connections' option to 'Mind Map'
  • Added 'Completed Date' to 'Attribute Inheritance'
  • Improved layout of overlapping 'Calendar' tasks
  • Improved handling of 'Due Task Notification' hyperlinks
  • Improved 'Time Tracker' task selection
  • Improved 'Edit Dependency' task selection
  • Improved performance of 'flat' tasklists

Introduction

You know how it is - you start work on one project and halfway through, you find one or two side-projects crop up that have to be solved before you can continue on the original project.

This is one such project with the added twist that it too started its life as a side-project. Here's what happened:

<Cue wavy screen effect>

I can only imagine that the planets must have been in (mis-)alignment or something, because at one point a few months ago, I was suddenly fielding emails on four or five separate articles I had previously submitted to CodeProject, some asking for features and others for bug fixes.

Foolishly or otherwise, I largely agreed with all the points raised, and subsequently found myself with fourteen or fifteen separate issues to resolve.

The situation was also made worse because I was trying to use CodeProject to keep track of all the things I had agreed to do, meaning that I had to continuously trawl the comments section of each article to remind myself of what I was supposed to be working on.

It even got to the stage where I was worrying that I'd fail to deliver on something - silly I know, but there you are!

Keeping a list on paper was a definite step in the right direction, but since I do all my coding on the same machine, it seemed somewhat inelegant, and anyway, we all know what happens to crucial bits of paper left lying around on desks and such.

The next step was to hunt around on the web for a tool to meet the following requirements:

  • Simple interface
  • Support for hierarchical data
  • Numbered items/subitems
  • Open file format
  • Freeware

Simple, huh! not!

I will admit that I did not spend weeks searching, but I am still surprised at the general lack of software matching my needs.

On reflection, I think that the reason may be simple: people are so used to commercial software being 'feature-rich' that when they come to design software themselves, they (not unreasonably) think they too need to cram as much in as possible, often leading to software where a lot of essential functionality is hidden away in the menu bar.

So, surprise, surprise, I decided to write something myself.

However, it's fair to say that I did not originally intend to post it on CodeProject and am only really doing so because I had a heap of fun solving some very interesting problems and these are what I think make it worth it.

Using the Software

There's really very little I need to say here since every feature/function is explicitly visible in the interface.

Nevertheless, the following list of basic capabilities and omissions may go someway to answering any questions that arise:

  • Files are stored in XML format with .xml file extension.
  • Trying to load a non-tasklist file will generally fail (unless you read the code to see how to circumvent it).
  • The number of items/subitems is limited only by memory (although performance may be the deciding factor before you exhaust memory).
  • Marking a parent item as 'done' will also gray-out child items, but they are not disabled or automatically marked as 'done'.
  • An ellipsis (...) indicates that an item has sub-items.
  • All items can be expanded or collapsed (by double-clicking).
  • Top-level items and sub-items are created using different toolbar buttons.
  • There are task-specific context-menus.
  • The previously open tasklists are re-opened on startup.
  • The tasklist is automatically saved when closing the software or minimizing it to the system tray.
  • The priority of a task is shown as a grayscale box to the left of the item.

Points of Interest

Here's where we come to the side-projects I was talking about, the first two of which I intend to work up into follow-up articles.

They are:

  1. The 'ordered' tree control, which incorporates a non-client gutter for displaying the item numbers.

    The idea stemmed from research I did into alternative designs for a tree-list control, which did not solve it by creating a hybrid control incorporating a tree and a list.

    The hybrid control seems such an obvious solution that I suspect few people have stopped to question it, but it has still always struck me as looking far too much like hard work to be truly elegant ('square pegs' and 'round holes' spring to mind).

    One possible idea is to implement the 'list' portion entirely in the non-client area of the tree. I.e., shift the right hand client edge to the left and then render the list portion in the resulting non-client area.

    Whilst I've yet to get round to building a proof of concept, it was nevertheless this ongoing mental debate which prompted me to try to solve the requirement for numbered items and subitems by rendering the item/subitem numbers in the non-client area.

    Without going into too much detail (as this will subsequently be an article of its own), this is how I got it to work:

    • Handle TVM_INSERTITEM and TVM_DELETEITEM to know exactly when items are added and removed.
    • In these handlers recalculate the width of the gutter required to display the widest 'dotted' item/subitem number. (Note: this is not necessarily simply the deepest subitem.)
    • If the required gutter width changes, call SetWindowPos(NULL, 0, 0, 0, 0, SWP_FRAMECHANGED | SWP_NOMOVE | SWP_NOSIZE | SWP_NOZORDER) to force Windows to recalculate the non-client area of the control.
    • Handle WM_NCCALCSIZE when it does, and offset the left border by the required gutter width.
    • Handle WM_NCPAINT for painting the numbers.

    This is necessarily an over-simplification, but it captures the essence of the solution, and all that essentially remains is lots of fiddling about to ensure the non-client area gets redrawn at the the right times to stay synchronized with the client area.

  2. Embedding .RC control definition data directly in a .cpp file to break the dependency on binary resources (a.k.a. 'Runtime Dialogs').

    This is an idea that has been floating about for quite some time and which has only recently gelled into a workable solution.

    The problem, put simply, is that if you want to take advantage of the resource editor in Visual Studio (and who doesn't), then you very quickly find yourself stuck with having to load dialog templates from resources compiled into the binary file.

    This further means that if you want to make use of a dialog across multiple projects, then either you need to copy and paste the dialog template between project .RC files, or you need to build the dialog into a DLL from which it can be accessed.

    'Runtime Dialogs' (a snappy title I coined myself) is a solution that neatly sidesteps both the nuisance of copying dialog resources between resource files and the extra work (and maintenance) involved in packaging dialogs in DLLs.

    And it works like this:

    • First, you design your dialog template in the resource editor, create a CDialog derived class using class wizard, and wire up all the controls just as you normally would.
    • Next, you #include "runtimedlg.h" and change all instances of CDialog to CRuntimeDlg.
    • Then, you cut and paste the control definition section from the appropriate section in the .RC file and embed it directly in the dialog's .cpp file as a static string (with a bit of tweaking to handle double quotes and such like).
    • Finally, in the constructor of your dialog, you simply call CRuntimeDlg::AddRCControls(...) passing the control definitions as a string.
    • And CRuntimeDlg takes care of the rest including, if required, auto-sizing the dialog to suit the control layout.

    I'm certainly not suggesting that this is a 'win-win' solution for all situations but it certainly has merits in its closer coupling of dialog template to dialog code which makes sharing dialogs across multiple projects a breeze.

    P.S.: In case it's not clear here, I used CRuntimeDlg to create CToDoCtrl which encapsulates the ordered tree together with the priority, date and comments controls as a single simple-to-instantiate control.

    I'm also proposing to use them in the .NET port of my ProjectZip add-in for VC6.

  3. Embedding the XML file in a web page.

    This is possibly the most satisfying aspect of the whole project because it was completely unexpected.

    What I mean is that, until recently, my knowledge of DOM and XMLDOM was virtually non-existent, as it's only since I've become more interested in the presentation of AbstractSpoon that I've been forced to get to grips with the various implementations of DOM and XMLDOM out there.

    I'm pleased to say that the code on my site works under IE 6.0, Netscape 7.1, and Mozilla, although custom code was required to achieve this.

Generic MFC Classes that may prove Useful to You

The following table lists a wide range of utility classes written for this project. They can all be included in any MFC project provided you include any class dependencies too. Feel free to ask any questions relating to these specific classes and how to use them.

Class Name

Description

Class Dependencies
(apart from MFC)

CAboutDlg

Customizable "About...' dialog not requiring a dialog resource. Supports html encoded text

CRuntimeDlg, CRCCtrlParser

CAutoComboBox

Adds only unique items to the drop list and shuffles the list so that the last added item is at the top

CHoldRedraw

CAutoFlag

Encapsulates the setting and unsetting of a boolean variable thru the lifetime of the class instance

 

CColorButton

Non-ownerdraw button that displays the selected colour on the button face and displays the colour dialog when clicked

CEnColorDialog

CColorComboBox

Owner-draw combobox for displaying and selecting user defined colours

 

CDateHelper

Encapsulation of various rountines for calculating date spans and for formatting

 

CDeferWndMove

Encapsulation of the Win32 API

 

CDialogHelper

Re-implementation of the CDialog DDX/DDV rountines to avoid the MFC error messages when the user clears a number edit (for instance)

 

CDlgUnits

Encapsulates the MapDialogRect Win32 API

 

CDockManager

Class for managing the docking of one popup window to another.

*CSubclassWnd, CHoldRedraw, CAutoFlag

CDriveInfo

Encapsulates various rountines for querying about drives, files and disk space

 

CEnBitmap

Adds support to CBitmap for loading non-bmp files and resources.

 

CEnBitmapEx, CColorReplacer, CImageBlurrer, CImageColorizer, CImageContraster, CImageEmbosser, CImageFlipper, CImageGrayer, CImageLightener, CImageNegator, CImageResizer, CImageRotator, CImageSharpener, CImageShearer, CImageSysColorMapper, CImageTinter

Adds image manipulation funationality to CEnBitmap

CEnBitmap

CEnColorDialog

Adds saving and restoring of custom colours to CColorDialog

 

CEnCommandLineInfo

Adds functions for extracting and querying commandline switches

 

CEnEdit

Adds user-defined button capabilities to CEdit

CMaskEdit, CThemed, CDlgUnits

CEnToolBar

Adds support for using alternative resource or file images

 

CFileEdit

Adds buttons for browsing and displaying the file represented by the text in the edit control. Also shows the file's small icon.

CEnEdit, CFolderDialog, CMaskEdit, CDlgUnits, CThemed, CSysImageList

CHoldRedraw

Encapsulates WM_SETREDRAW

 

CHotKeyCtrlEx

Fixes a number of behavioural problems including the handling of certain keypresses

 

CHotTracker

Tracks the cursor movement over user-defined windows and posts event messages as necessary

*CSubclassWnd,

CLimitSingleInstance

Provides simple method to detect if another instance of an app is running

 

CMaskEdit

Adds simple character masking to CEdit

 

CNcGutter

Allows the UI of standard windows controls to be extended by supporting any number of columns to be added to the non-client area of the window. Favours tabular controls like lists, trees, etc

*CSubclassWnd, CHoldRedraw, CThemed, CDlgUnits

COrderedTreeCtrl

CTreeCtrl implementation of CNcGutter displaying a single column showing the hierarchical position of each tree item in '1.2.3.4' notation.

CHoldRedraw, CThemed

CPasswordDialog

Very simple password dialog not requiring a dialog resource

CRuntimeDlg, CRCCtrlParser

CPropertyPageHost

Simpler replacement for CPropertySheet allowing easier creation as a child window

 

CRCCtrlParser

Used by CRuntimeDlg for parsing dialog resource-like text

 

CRuntimeDlg

Adds support to CDialog for building dialogs at runtime ie. dialogs do not require a dialog resource

CRCCtrlParser

CShortcutManager

Class for handling application keyboard shortcuts.

*CSubclassWnd, CWinClasses

CSpellCheckDlg

Spellcheck dialog not requiring a dialog resource, which interfaces with ISpellCheck (interface to Open Office dictionaries)

CRuntimeDlg, CRCCtrlParser, ISpellCheck

CSysImageList

Encapsulates the Windows system image list (file/folder images)

 

CTabCtrlEx

Adds post rendering callback for the tabs without using owner-draw

 

CThemed

Encapsulates themed (XP) and non-themed (the rest) drawing of windows controls

 

CTimeEdit

Adds a button for specifying time units and provided routines for converting time to and from different time units

CEnEdit, CMaskEdit, CThemed, CDlgUnits

CToolbarHelper

Adds support for dialog toolbar tooltips, multiline tooltips and dropbuttons with menus

*CSubclassWnd, CEnBitmap, CEnBitmapEx

CTrayIcon

Encapsulates the Shell_NotifyIcon Win32 API. Also provides balloon tips and animation

*CSubclassWnd,

CUrlRichEditCtrl

Adds support for recognizing urls, clicking them and setting custom url callbacks

 

CWinClasses

Encapsulates the ::GetClassName Win32 functions

 

CXmlFile, CXmlItem

Non-Unicode class for reading and writing xml files

 

CXmlFileEx

Adds encryption capabilities to CXmlFile

CXmlFile, IEncryption

* CSubclassWnd was originally written by Paul DiLascia for MSJ magazine. The version I use has been heavily extended to suit my specific needs. The classes that depend on it here need this extended version.

Further Work

Whilst this tool was originally intended for my personal use only, it is now a 'community' project, so if you find it useful and want to make suggestions for enhancements or bug fixes, please post to our Google Group.

History

  • History now held here
  • 1.1-7.1 (removed by .dan.g.)
  • 1.0 (4 Nov 2003)

License

This article, along with any associated source code and files, is licensed under The Eclipse Public License 1.0


Written By
Software Developer Maptek
Australia Australia
.dan.g. is a naturalised Australian and has been developing commercial windows software since 1998.

Comments and Discussions

 
GeneralRe: Import calendar from outlook? Pin
Pierre de la Verre24-Nov-13 12:21
Pierre de la Verre24-Nov-13 12:21 
GeneralRe: Import calendar from outlook? Pin
Armando TDL25-Nov-13 0:44
Armando TDL25-Nov-13 0:44 
QuestionToDoList is 'ugly' (Part 2) Pin
.dan.g.22-Nov-13 15:41
professional.dan.g.22-Nov-13 15:41 
AnswerRe: ToDoList is 'ugly' (Part 2) Pin
Armando TDL23-Nov-13 6:33
Armando TDL23-Nov-13 6:33 
AnswerRe: ToDoList is 'ugly' (Part 2) Pin
akaDormouse23-Nov-13 6:37
akaDormouse23-Nov-13 6:37 
AnswerRe: ToDoList is 'ugly' (Part 2) Pin
Jean-Marc FR23-Nov-13 7:21
Jean-Marc FR23-Nov-13 7:21 
AnswerASANA Pin
Armando TDL23-Nov-13 8:01
Armando TDL23-Nov-13 8:01 
AnswerRe: ToDoList is 'ugly' (Part 2) Pin
_BS_23-Nov-13 16:04
_BS_23-Nov-13 16:04 
(Please pardon the length, I guess there's a bit of passion coming out, here.)

For me TDL is beat, out of the box, for reasons that have very little to do with the program itself:

- it's intimidating, or, as some say, busy

- for some reason I can't fathom, the concept of sub-tasks is difficult / non-intuitive to understand for the phone / tablet generation. This is the only reason I can think of as to why every task manager on the planet doesn't have the concept of sub-tasks baked into the very premise of the effort. How can the concept of grocery list not have inherently required a Meat subsection, is beyond me.(Just try transforming a recommended daily allowances / food guide on top of a grocery list, and not have to try and figure out do you have enough portions for X number of meals for Y number of people, across Z number of days, broken down by food group! Sadly, neither beer nor desert classify as food groups. Sub-groups, or contexts ... arguable.)

- Palm (I'll guess) made the PIM popular. Tasks (TDL) are the least favourite cousin of the PIM, especially if you try to define a line between event calendar entries (pick up milk), project planning (go shopping), and todo's, some of which are context and time sensitive. (You have a task list of which some portion of entries have corresponding contextual calendar entries. OK, I'm getting groceries, and there's a pharmacy in the same mall. And bring home pizza.)

- it's the ecosystem that surrounds TDL more than TDL itself. Aside from the PIM / calendaring aspects, where is the user community (the user community, not the programmer or geek community), mutual support, documentation, and so on. i.e. All the things that cost money that Dan.G's not interested in (nor should he be, if coding is his thing) - except, wait for it, it's a free program. There's no wonder this isn't as around or as pretty as other -commercial- products. Nor should it be. But the ecosystem lack holds TDL back. pbworks nothwithstanding - which for years I've seen hasn't been touched in years. (Working on this, now.)

- so, for TDL to be more successful, at least at an introductory / superficial level, it must integrate into other PIMs out there. [Don't even mention Outlook - I will not ever own it.] If Palm introduced and made popular the PIM, then the world spun backwards when it introduced Android. No PIM, local sync., all of that rich, good, user happy stuff, got left by the wayside. Google calendar is a joke (can't even tick off a task as being completed), Google tasks is even worse - so many attributes missing and anyone thinking Google will ever do anything with it is fantasizing somewhere I don't want to be near. Even ToodleDo, apparently reasonably popuplar (and 'pretty', vis a vis TDL, but not MLO), is able to get away with subtasks that aren't. For money even. Summary: There is no PIM ecosystem out there for TDL to integrate into. There's only the web 2.0 app nonsense that has lost local storage of my own data, tight / easy to use interfaces, keystroke oriented.

- What is TDL? It's a project manager (ick, intimidating), no, wait, it's a list manager (less intimidating), no it's a life manager, it's a goal roadmap, it's a todo list keeper, it's a tasklist manager (never mind the apparently intellectual exercise necessary to understand that tasks are todos and vice versa), it's a GTD system (a wha?), it's a ... WHAT THE HECK IS IT??? It's all of those things, in a generic, universal interface. Which makes it hard to suck up and realize I want to spend many hours here because IT WILL MAKE MY LIFE BETTER!

- Dropbox coming along, and Android app., since (see, world moving along), has brought me back to TDL. So, I have a way to keep (cross-platform and cross-computer, because of external forces), share with my TEAM, and some of the ecosystem misses in today's world are now present. To TDL's benefit! And all beyond the control, and necessary expenditure of effort, of TDL. So leverage / publicize it - 'it fits within your current workflow and makes your life better! Buy today! Quantities are limited! Comes in chocolate too!)

Having said this, some easy things to do:

- start a google group, or something. Better with a wiki. pbworks appears nice enough at start, but is missing lots. More user driven than not - Dan.G. need not watch it every other second. [Note: This is not in place of this forum. Or pbworks, or at least not yet.] Start pulling together the rich user community experience to leverage off each other - particularly the non-geeks and coders. Google todolist and you'll find references on all sorts of web sites - instead of one major one-stop shopping TDL info central.

- right-click a task and post to my google calendar - equivalent to 'share as' present in Android - both TDL and MLO. I say Google only because it has become ubiquitous, no matter how bad the functionality is. (Go figure.) Which is to say, anything that comes out on a go forward basis is going to be Google aware - or that anything else is going to go nowhere. Anything more can come elsewhen - (storage in google docs, etc., as present, is wonderful - except the Android app says it can't save to docs, only Dropbox). Storage is NOT PIM integration. So Google Calendar and Tasks integration (you'd be the first app I know of to integrate what should never have been separate in the first place - Google subtasks with dated items appearing in the calendar simultaneously.) Why does this matter? Because everything else in the world is now keying off Google (only thing out there). Be it colours, presentation, alerts, widgets, sharing - you name it. And TDL would come along for the ride. (Heck, integrate / merge with Pimlical - subtasks are the only thing it's missing. Not saying Pimlical is all there yet, but their history shows they know what's what and are actively working towards where the world already was - in Palm, that disappeared with Android and Google. Just, like TDL, there's only so many programmers available and hours in a day.

- change preferences to have one (left) line (tab?) per right-window. It took me far too long to realize when I clicked on the 2nd left line I was still in the same window on the right as when I was on the top line. When I first encountered this years ago, my gut started telling me I wasn't in a program I wanted to spend hours of my life in. It all makes sense once you're used to it, but it's not intuitive / consistent with other software, even it is easier to program - and having encountered it, one starts looking askance at every other aspect of the program. Just about the first thing I do with any new piece of software is look at the preferences.

- change the default view at first open to maximized with notes, checkbox and title only. Take the intimidation factor away. Let them sink into that much of TDL before going deeper. Anyone looking for more will have seen the possibilities in screenshots or wherever, and know it's in there, they just have to turn something on - or they wouldn't be trying TDL in the first place. Include an initial popup of 'press Esc for detailed view' or something.

- here's an idea just thought of, see if it resonates. One comes to TDL looking for 'a something', to solve a need - not a Swiss Army knife of incredible functionality and flexibility. Don't want to call this themeing, but, what if an initial (install?) dialogue asked what you're initially looking to do with TDL? If it's 'todo/list/task manager' set some default preferences / initial views appropriately. e.g. Little or no date columns, maximized with notes view, etc. If it's 'project management' then a different initial view results, with many date fields visible. No doubt there are others, but can the extraneous, intimidating, 'not what I'm here for' aspects of "I'm trying this software because" aspects be removed - at least long enough to get comfortable and realize, YES, this IS where I really want to be.

- I hesitate to say this, in this so called paperless age, but could a print (output) wizard be created? a la Report Writers. (Custom headers, templates, etc. Think old dBase 3, or even LibreOffice Base.) No man lives alone, and one doesn't come to such software as TDL if they're not working with others, really. So, in some fashion I'm going to share with someone this is my list, or this is some wonderful software I'm using ... see? And every time someone shows such to someone else, they're starting to evaluate whether or not TDL would be useful to them. If that demonstration looks tightly applicable, clean and easily integrates into their own current workflow, to their particular use case, then you've just acquired another user. But I won't even show it to you if ... (and the word on the wonderfulness of TDL doesn't get spread around as much as it otherwise might).


The program is solid, its GUTS are magnificent. It's interface is clean and simple, which REALLY attracts me to it and keeps me coming back. But software does not live by code alone - it must integrate with the rest of one's life, including calendars. And that is a continuously moving target - witness today's prevalence of Android and Google. Neither of which were predictable in Palm's heydey. And somehow the world went backwards, post-Palm, losing established functionality in Google, yet somehow being so successful as to have become ubiquitous. I believe the era of standalone non-integrated software is gone. And web 2.0 apps (read, subscription revenue for program development costs) becoming all pervasive - sadly. The latter also meaning it is no longer sufficient to code well only - one must have graphics artists, marketers, and support contributors surrounding them. Even if I only want to code, and there already aren't enough hours in the day.

Thank you again, Dan. G., for being here!

CDN$0.02
GeneralRe: ToDoList is 'ugly' (Part 2) Pin
zajchapp23-Nov-13 23:30
zajchapp23-Nov-13 23:30 
GeneralRe: ToDoList is 'ugly' (Part 2) Pin
_BS_24-Nov-13 6:07
_BS_24-Nov-13 6:07 
GeneralRe: ToDoList is 'ugly' (Part 2) Pin
.dan.g.25-Nov-13 16:44
professional.dan.g.25-Nov-13 16:44 
GeneralRe: ToDoList is 'ugly' (Part 2) Pin
_BS_26-Nov-13 8:03
_BS_26-Nov-13 8:03 
GeneralRe: ToDoList is 'ugly' (Part 2) Pin
Armando TDL24-Nov-13 2:50
Armando TDL24-Nov-13 2:50 
AnswerRe: ToDoList is 'ugly' (Part 2) Pin
_BS_24-Nov-13 14:03
_BS_24-Nov-13 14:03 
AnswerRe: ToDoList is 'ugly' (Part 2) Pin
zajchapp25-Nov-13 22:40
zajchapp25-Nov-13 22:40 
GeneralAWESOME Pin
Carlos Gant21-Nov-13 3:35
Carlos Gant21-Nov-13 3:35 
GeneralRe: AWESOME Pin
.dan.g.21-Nov-13 13:32
professional.dan.g.21-Nov-13 13:32 
QuestionQuestion about printing Pin
Member 1005239621-Nov-13 3:01
Member 1005239621-Nov-13 3:01 
AnswerRe: Question about printing Pin
Pierre de la Verre21-Nov-13 9:09
Pierre de la Verre21-Nov-13 9:09 
GeneralRe: Question about printing Pin
Member 1005239622-Nov-13 2:20
Member 1005239622-Nov-13 2:20 
GeneralRe: Question about printing Pin
Pierre de la Verre22-Nov-13 3:02
Pierre de la Verre22-Nov-13 3:02 
GeneralRe: Question about printing Pin
.dan.g.22-Nov-13 15:50
professional.dan.g.22-Nov-13 15:50 
GeneralRe: Question about printing Pin
.dan.g.22-Nov-13 15:50
professional.dan.g.22-Nov-13 15:50 
GeneralRe: Question about printing Pin
Member 1005239623-Nov-13 1:52
Member 1005239623-Nov-13 1:52 
AnswerRe: Question about printing Pin
.dan.g.21-Nov-13 13:34
professional.dan.g.21-Nov-13 13:34 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.