printing source code in Crossworks 2

Started by Bruce March 5, 2010
I wanted to see if anyone had experienced a problem printing their source code in Crossworks. This is Crossworks 2 on Ubuntu Linux. When I select print there are no printers listed even though they show up in other applications. I tried to get Rowley to work the issue but Paul says it is probably a problem with the software he uses to make Crossworks with. To give him a fair shake I'll download a copy of the trouble ticket over the issue to the files area as a pdf. It is named: CrossWorks_Support__Request_1280_printer_list_.pdf'

If anyone has experienced the same issue I would like to know especially if you have a fix.

An Engineer's Guide to the LPC2100 Series

--- In l..., "Bruce" wrote:
>
> I wanted to see if anyone had experienced a problem printing their source code in Crossworks. This is Crossworks 2 on Ubuntu Linux. When I select print there are no printers listed even though they show up in other applications. I tried to get Rowley to work the issue but Paul says it is probably a problem with the software he uses to make Crossworks with. To give him a fair shake I'll download a copy of the trouble ticket over the issue to the files area as a pdf. It is named: CrossWorks_Support__Request_1280_printer_list_.pdf'
>
> If anyone has experienced the same issue I would like to know especially if you have a fix.
>

I don't know about a 'fix' but it does work on my Ubuntu 9.10 system. I only have 2 printers defined and both show up in the Print dialog.

Richard

Hi,

> I wanted to see if anyone had experienced a problem printing their
> source code in Crossworks. This is Crossworks 2 on Ubuntu Linux. When I
> select print there are no printers listed even though they show up in
> other applications. I tried to get Rowley to work the issue but Paul
> says it is probably a problem with the software he uses to make
> Crossworks with. To give him a fair shake I'll download a copy of the
> trouble ticket over the issue to the files area as a pdf. It is named:
> CrossWorks_Support__Request_1280_printer_list_.pdf'

Man, go for it! Publish and be damned. :-) I don't get embarrassed
easily, and I've been straight as a die with you in my private responses
which you seek to publish.

So, more power to you to get that ticket in view, no redactions, no
editing, verbatim, OK? But then it seems to, um, incomplete. There was a
bit after that discussion. So, please, if you wish to drag this in public
in the spirit of "giving me a fair shake", at least publish the FULL
TRANSCRIPTION of that conversation will you? My response did not waiver:
it's a minor feature with a simple work-around that you wish to escalate.
As I said, if it had been a problem in something I can control, that
impaired CrossWorks' major facet of building and debugging code across a
huge range of microcontrollers, Completely Different Matter.

All over a $150 personal license purchase. Makes me wonder why I offer
our software so cheaply or on such preferential terms. Really. Why do it
for this aggravation? Screw it. I'll just kill the personal licenses and
all the free hardware and software I've given to support members of this
group without asking for anything in return.

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks V2 is out for LPC1700, LPC3100, LPC3200, SAM9, and more!
I'll still be your "voice of praise". You have a helluva product and
phenomenal support. I'm always happy to recommend the development
system and your hardware whenever I can.

I don't think I have ever - even once - printed from within
Crossworks. And I would think that it is probably the Linux setup that
does those things.

-Rob

> Hi,

>> I wanted to see if anyone had experienced a problem printing their
>> source code in Crossworks. This is Crossworks 2 on Ubuntu Linux. When I
>> select print there are no printers listed even though they show up in
>> other applications. I tried to get Rowley to work the issue but Paul
>> says it is probably a problem with the software he uses to make
>> Crossworks with. To give him a fair shake I'll download a copy of the
>> trouble ticket over the issue to the files area as a pdf. It is named:
>> CrossWorks_Support__Request_1280_printer_list_.pdf'

> Man, go for it! Publish and be damned. :-) I don't get embarrassed
> easily, and I've been straight as a die with you in my private responses
> which you seek to publish.

> So, more power to you to get that ticket in view, no redactions, no
> editing, verbatim, OK? But then it seems to, um, incomplete. There was a
> bit after that discussion. So, please, if you wish to drag this in public
> in the spirit of "giving me a fair shake", at least publish the FULL
> TRANSCRIPTION of that conversation will you? My response did not waiver:
> it's a minor feature with a simple work-around that you wish to escalate.
> As I said, if it had been a problem in something I can control, that
> impaired CrossWorks' major facet of building and debugging code across a
> huge range of microcontrollers, Completely Different Matter.

> All over a $150 personal license purchase. Makes me wonder why I offer
> our software so cheaply or on such preferential terms. Really. Why do it
> for this aggravation? Screw it. I'll just kill the personal licenses and
> all the free hardware and software I've given to support members of this
> group without asking for anything in return.

Do you use Crossworks 2?










Here is the rest of the conversation:





> Paul Curtis, Mar 05 07:12 pm (GMT):

> It is a
minor feature in my view--it does not impair CrossWorks core function.
I have better things to do than chase > down bugs in Qt
and/or Ubuntu
8.04 and why Qt 3.3.6 does not work with it, and I've said as much. You
would think I > serve you better by say "I'll look at it" and
then just
forget it? Nope. I've told you straight: it's just not a priority and

> there are better formatters offering 2-up and many other
features.


> Now, if it had been a debugging issue, that would be worth
some
attention because it's a core issue and something I > have
control over.


> I'm not taking the bait about promoting into the workplace
either;
the response would have been the same: I am not > fixing this,
it's not a
major issue, it can wait until a bug fix release of Qt arrives, if
ever.


> I've been straight and told you the reality of the
situation. It's
unfortunate that our views differ, but I can live with

> that.



style="border-style: dashed none none; border-color: rgb(194, 194, 194) -moz-use-text-color -moz-use-text-color; border-width: 1px 0pt 0pt; margin: 15px 0pt 0pt; height: 1px;">

I think most would agree with me, if they read the correspondence, that
it is not that you won't or can't fix it. For the sake of being fair
I'll believe that you can't fix it. That is not my biggest problem with
the way you treated it. It was your attitude.



If you had said that due to the nature of the way the Crossworks
program was written, someone else's code is messed up. We will work
with them to get it fixed if possible. I would not have had a problem
with that. But you told me, when I asked you what QT and Trolltech were
you responded with:



Qt is what we use to write our GUI in. Trolltech coded the Qt GUI
toolkit. Nokia make phones and own Trolltech. Google answers
questions.




It is an issue I would like to resolve if possible with help from
people that don't mind helping. Richard uses Ubuntu 9.1 and says his
works fine. That is an idea I would like to pursue.







Paul Curtis wrote:

Hi,



I wanted to see if anyone had experienced a problem printing
their  
source code in Crossworks. This is Crossworks 2 on Ubuntu Linux. When I
select print there are no printers listed even though they show up in
other applications. I tried to get Rowley to work the issue but Paul
says it is probably a problem with the software he uses to make
Crossworks with. To give him a fair shake I'll download a copy of the
trouble ticket over the issue to the files area as a pdf. It is named:
CrossWorks_Support__Request_1280_printer_list_.pdf'



Man, go for it! Publish and be damned. :-) I don't get embarrassed
easily, and I've been straight as a die with you in my private responses
which you seek to publish.

So, more power to you to get that ticket in view, no redactions, no
editing, verbatim, OK? But then it seems to, um, incomplete. There was a
bit after that discussion. So, please, if you wish to drag this in public
in the spirit of "giving me a fair shake", at least publish the FULL
TRANSCRIPTION of that conversation will you? My response did not waiver:
it's a minor feature with a simple work-around that you wish to escalate.
As I said, if it had been a problem in something I can control, that
impaired CrossWorks' major facet of building and debugging code across a
huge range of microcontrollers, Completely Different Matter.

All over a $150 personal license purchase. Makes me wonder why I offer
our software so cheaply or on such preferential terms. Really. Why do it
for this aggravation? Screw it. I'll just kill the personal licenses and
all the free hardware and software I've given to support members of this
group without asking for anything in return.













__._,_.___
On Fri, 05 Mar 2010 22:32:48 -0000, Bruce Lindsay
wrote:

> I think most would agree with me, if they read the correspondence, that
> it is not that you won't or can't fix it. For the sake of being fair
> I'll believe that you can't fix it. That is not my biggest problem with
> the way you treated it. It was your attitude.

You will always find me direct and to the point. There is no point to
floury prose.

> If you had said that due to the nature of the way the Crossworks program
> was written, someone else's code is messed up. We will work with them to
> get it fixed if possible.

I would not have said that as that does not represent reality and hence is
it not the truth. The reality is that it will not get resolved at all,
ever.

> I would not have had a problem with that.

You are wishing for me to issue a response that I cannot stand behind.
The reality is that it cannot, and will not, be investigated nor fixed, by
me or Nokia.

> But you told me, when I asked you what QT and Trolltech were you
> responded with:

Don't forget you also asked about Nokia...

> Qt is what we use to write our GUI in. Trolltech coded the Qt GUI
> toolkit. Nokia make phones and own Trolltech. Google answers questions.

I am simply making a point that you can find the answers yourself with
Google. I concisely answered your questions.

> It is an issue I would like to resolve if possible with help from people
> that don't mind helping. Richard uses Ubuntu 9.1 and says his works
> fine. That is an idea I would like to pursue.

Change OS to print from CrossWorks? The world is clearly not as I had
envisaged. Any pragmatist would just find a better print formatter for
source code on Linux and leave it at that.

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks V2 is out for LPC1700, LPC3100, LPC3200, SAM9, and more!
Hi Rob,

> I'll still be your "voice of praise". You have a helluva product and
> phenomenal support. I'm always happy to recommend the development
> system and your hardware whenever I can.

Yeah, I love answering tickets at 11:25pm on a Friday, because, gee, I
have it real easy in the day job. ;-)

> I don't think I have ever - even once - printed from within
> Crossworks. And I would think that it is probably the Linux setup that
> does those things.

Perhaps I just need to pull it then? Fewer things to go wrong. Better
printing doesn't appear on the User Voice pages, so doesn't even make it
onto the development radar.

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks V2 is out for LPC1700, LPC3100, LPC3200, SAM9, and more!
On Sat, Mar 6, 2010 at 5:23 AM, Paul Curtis wrote:
> All over a $150 personal license purchase. Makes me wonder why I offer
> our software so cheaply or on such preferential terms. Really. Why do it
> for this aggravation? Screw it. I'll just kill the personal licenses and
> all the free hardware and software I've given to support members of this
> group without asking for anything in return.
>

Hmm, business is business. If you found it does not serve your
purpose (presumably enlarge your customer base and hopefully
earn money in the long run), just kill it.

If you keep it, then you have to support it. And if the extra
work overweight the benefits, then you may want to kill it.
But sometime the benefits are difficult to measure.
--
Xiaofan http://mcuee.blogspot.com
Hi,

> Hmm, business is business. If you found it does not serve your
> purpose (presumably enlarge your customer base and hopefully
> earn money in the long run), just kill it.

My reasons for offering personal licenses are well documented, I hardly
need to restate them.

> If you keep it, then you have to support it. And if the extra
> work overweight the benefits, then you may want to kill it.
> But sometime the benefits are difficult to measure.

Personal licenses are sold without any form of guaranteed support: I do
not *have* to support such licensees, but I *do* choose to. For
Educational Licenses we expect tutors to assist students, not us. For
Commercial Licenses we support customers well beyond their expectations on
longevity of support and the type of support we give.

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks V2 is out for LPC1700, LPC3100, LPC3200, SAM9, and more!