Re: [Kxstitch-users] Request for enhancement - Total stitch count.

[Robin L. <MeSat@TelusPlanet.net>]

Stephen Allewell wrote:
> Robin Laing wrote:
>> Stephen Allewell wrote:
>>> Robin Laing wrote:
>>>> Hello,
>>>>
>>>> My wife loves your program and is using it almost daily.
>>>>
>>>> She is making a list of wishes to make the program better.  One of them
>>>> is a total stitch count for each type of stitch.
>>>>
>>>> I am not familiar with C++ programming but I am looking at the source
>>>> code which I downloaded yesterday.
>>>>
>>>> I am making some assumptions in my suggestion.
>>>>
>>>> You are using a data array to store the stitch values and counts.  In
>>>> the palletview.cpp, around lines 308-327, is the print routine for the
>>>> floss page.
>>>>
>>>> In this routine, the individual columns are printed for the various
>>>> stitch counts, full, half, quarter, three quarter, knots and backstitch.
>>>>
>>>> Would it be possible to add one last line to this routine to total each
>>>> one of these stitches and print it?
>>>>
>>>> Something like
>>>>
>>>> full_total = full_total + arg(usageMap[m_flosses[floss]].full)
>>>> half_total = half_total + arg(usageMap[m_flosses[floss]].half)
>>>> quarter_total = quarter_total + arg(usageMap[m_flosses[floss]].quarter)
>>>>
>>>> etc
>>>>
>>>> And then print the totals out before starting to print the next page at
>>>> the bottoms of each stitch column.
>>>>
>>>> Robin
>>> Robin
>>>
>>> I have done a rough bit of coding which produces the output shown in the
>>> attached image.  Is this the kind of thing you want?  If so I will
>>> commit the change to CVS.  Otherwise let me know what you want changing.
>>>
>>> Regards
>>>
>>> Steve
>>>
>>>
>>> ------------------------------------------------------------------------
>> Hello Steve.
>>
>> Quick response.
>>
>> My wife looked at it and it would be fine this way or as a summary at
>> the bottom of each column.
>>
>> I think the summary at the bottom of each column would be better if the
>> number of floss types was higher.  Sort of like a summary row in a
>> spreadsheet.
>>
>> Either way is great.
>>
>> As my wife said, knowing the number of stitches allows for estimation of
>> time needed to complete a project.  She spends the time totally each
>> stitch on every print out.
>>
>> BTW, what do you use for an IDE for your c++ programming?
>>
>>
>> Robin
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Kxstitch-users mailing list
>> Kxs...@li...
>> https://lists.sourceforge.net/lists/listinfo/kxstitch-users
>>
>>
>>
> 
> I can do it either way.  I can even do it both ways with a user
> checkable option in the print dialog.  Whatever suits you really.
> 
> As for programming, I started out with kdevelop, but now just use a text
> editor, kwrite or vim depending on my mood.
> 
> Regards
> 
> Steve
> 

Steve,

My wife and I think that by column should be the default but both as an
option is great.  In fact better as it gives the user a choice.  And I
think choice is nice.

I started with Emacs ages ago and I just have stuck with it.  I have
tried other programs but I seem to keep coming back to Emacs.  I will
use a GUI text editor when I want special printing.  It has been decades
since I took a C course and now I need to get back into it.  One reason
I took a look at the source code.

Robin