Re^9: pp with gui (debug without --gui)

[marto]

"I explained in another post why I haven't had a lot of time to work with this. Under normal circumstances yes it would be good to learn the tool inside out and only then ask questions."

So your logic is that your time is limited, rather than follow instructions on how to best resolve your problem or even get help for it you choose to ignore this, and continue to run into problems. This plan isn't working out well for you so far.

"I have done everything that I knew or figured out how to do (read the old posts). I have been sending the output as I do them in hopes it will point someone more knowledgeable to the problem."

Not true, you've been given lots of advice that you've ignored, time and time again, and posted no output, error or warnings. Most recently here where you ignore the advice about not hiding runtime errors and ignoring problems. If you don't want peoples help in solving a problem, stop asking.

"What is the sense of me going step 1 though 10 if someone could have looked at step 5 and saw the problem."

Had you bothered to do so you'd be further forward. You have a problem to solve, you have to debug this, albeit as instructed by others. If you don't want to do this I suggest a change of career, as computer programming involves a lot of this.

[mkmal]

My logic is that I will spend what time I can fixing this. Some of the things asked of me I don't know how to do yet. In another post I thanked the monk who gave me pointers and stated that I will read up on what he gave me. Did you read that?

>>Not true, you've been given lots of advice that you've
>>ignored, time and time again, and posted no output, error
>>or warnings. Most recently here where you ignore the advice
>>about not hiding runtime errors and ignoring problems. If
>>you don't want peoples help in solving a problem, stop
>>asking.

You just proved my point. You did not read my post. I did provide the output you said here

http://perlmonks.org/index.pl?node_id=1026405

[Anonymous Monk]

Now turn on the PAR debugging option so we can debug PAR problems

[marto]

"My logic is that I will spend what time I can fixing this. Some of the things asked of me I don't know how to do yet. In another post I thanked the monk who gave me pointers and stated that I will read up on what he gave me. Did you read that?"

Obviously I read that, hence why I pointed out that you're ignoring this. In this thread you've been given a lot of advice you've repeatedly ignored. Everything below this part of the thread, Re: pp with gui, this, here, I could go on. Where's the effort you are making? You don't seem to be doing any investigation yourself ("What is the sense of me going step 1 though 10 if someone could have looked at step 5 and saw the problem"), you're ignoring steps provided and actually taking a step back. This is pointless.

"You just proved my point. You did not read my post. I did provide the output you said here"

You've proven nothing. Obviously I read that post, I replied to it pointing out that you're ignoring the advice given, again and again. If you're simply here to vent your frustration, you're wasting more of your time. Also that's not how you link to things here, What shortcuts can I use for linking to other information?.

Rather than post again, the same meaningless information, a quip about how little time you have, a repost or another instance of building this executable where you ignore what everyone has told you so far, I suggest you sit down and actually read* the pp documentation, read the hints and tips in this thread, read the posts linked to. Actually make notes about what you're doing. Use the debugging and error checking you've been told about (multiple times), in short make some effort. It's called debugging. It's part of the job, if you don't like doing it I suggest you consider an alternate passtime/career.

* when I say read, I mean read and understand.

[mkmal]

I don't have the time to properly look into this so I will just table it for now. When I originally posted I hoped it would be something simple. It is not and this is a very low priority issue for me.
Given that I will table this issue for now until I can give it the proper attention.

I will note however that you did say

>>Not true, you've been given lots of advice that you've
>>ignored, time and time again, and posted no output, error
>>or warnings. Most recently here where you ignore the advice
>>about not hiding runtime errors and ignoring problems.

So you clearly said that I did not show the runtime error when running without --gui.
There have been some things like turning on debug that I did not do. That was simply because I haven't figured out how yet. I don't usually program on windows and I am fairly new to Perl.

Now you say


>>Obviously I read that post, I replied to it pointing out
>>that you're ignoring the advice given, again and again.

So you clearly said I didn't do something that I showed you I did and now you say you didn't do that. Problem is the posts say otherwise.

Also, telling someone they need to go into another line of work based on a few posts is silly.
The people who actually pay me to program have been giving me great reviews for many years so your opinion of what I should do for a living of little importance to me.

I am done posting and reading this thread. I may open a new one once I can dedicate more time to this. To those that were trying to be helpful my sincere thanks. To those who just wanted to be critical cheer up. There are other posts you can attack.

[marto]

"So you clearly said that I did not show the runtime error when running without --gui."

Nope, clearly you're having difficulty following responses to your own thread. Hardly surprising given your input.

"So you clearly said I didn't do something that I showed you I did and now you say you didn't do that. Problem is the posts say otherwise."

Wrong again, I've linked to specific posts where you continue to make the same mistake, you link to nothing and provide no evidence to back up this false claim. In one part of the thread you show errors without using -gui, your next post you're back to using it again without actually addressing the problems. Please post facts, not fantasy.

"There have been some things like turning on debug that I did not do. That was simply because I haven't figured out how yet. I don't usually program on windows and I am fairly new to Perl.

The modules you're using are cross platform, the packager you're using is cross platform, you'd have the same issue regardless of the platform you'd be packaging on. You're new to perl, fine, all the more reason to take the advice you asked for from those who aren't new to perl, or the tasks you're attempting. For reference the pp documentation is ~2.5k words in total, this shouldn't take you long to read. even if you didn't want to read all of it finding the pertinent parts and reading only them would take even less time. You've been given links here explaining how to achieve all this, you "haven't figured out yet" because you didn't bother looking. This isn't hidden information. Rather than spend the time doing some work you're back here wasting time with a post like this, making things up, seemingly blaming others for your lack of progress.

"Also, telling someone they need to go into another line of work based on a few posts is silly."

Like your lack of code, nonexistent debugging effort and incoherent ramblings, I can only work with what you give me. Your decision to continually ignore advice, and not actually do any debugging suggests that you don't have the patience to do what you're trying to do, or at best you need to work on this, however you continue to waste time with arguments about why you don't know things rather than invest the time in learning. Nobody is born knowing any of this, everyone has to learn it.