Why does this not work?

[Gensek]

(I don't know how to make the title more specific in a useful way,
sorry.)

http://www.geocities.com/fusionary_2000/PingGUI.zip

Requires wxPython.

The part that fails is the function OnGridLabelLeftClick in PingGUI.py.
It just doesn't do anything. It's supposed to sort the grid by values
in the column that was clicked.

Why?

 

[Peter Hansen]

(I don't know how to make the title more specific in a useful way,
sorry.)

Here's a hint: take a moment to look over your post
just before you send it, and pick at least one of
the specific details therein.

In this case, "problem with PingGUI" would have been
most helpful in (a) letting those of us who know nothing
about it skip over your message, and (b) letting those
of us who know nothing about it read your message to
learn something about a package that's new to us, if
we felt so inclined.

"problem with OnGridLabelLeftClick in PingGUI" would have
been even better...

 

[Gensek]

PingGUI is a program that nobody but me knows anything about. If I
wanted help from people who are experts on it, I'd get nothing at all.

 

[Michael Hoffman]

PingGUI is a program that nobody but me knows anything about. If I
wanted help from people who are experts on it, I'd get nothing at all.

It appears as if that's the situation anyway, at least so far. But you
want wxPython help so you should ask for that instead. Something like
"Why doesn't this function re-sort my wxPython grid?"

Also, very few people are going to go to the trouble of downloading your
zip. I know I'm not. You need to post the smallest possible snippet of
code that you are having trouble with.

I would respectfully suggest you read this excellent document. The
suggestions will help you get help:

http://www.catb.org/~esr/faqs/smart-questions.html

Then come back and post something with a sensible subject and you will
probably get some more direct help.

 

[Gensek]

Thanks, guys, it works now. I couldn't have done it without your
generous help.

 

[D H]

Thanks, guys, it works now. I couldn't have done it without your
generous help.

Ask on the wxpython or python-tutor list instead of this one. You'll
get better help than there as you've already found out.
The only thing I'd agree with is what Michael Hoffman said about posting
a snippet of your code instead of a zip file.

 

[Gensek]

I fixed it already, as I said. The problem had nothing to do with
wxPython. I just used my own functions in the wrong way.

 

[Michael Hoffman]

Thanks, guys, it works now. I couldn't have done it without your
generous help.

You're welcome! Any time.

 

[Peter Hansen]

Ask on the wxpython or python-tutor list instead of this one. You'll
get better help than there as you've already found out.

Not likely. IMHO he got the best help he could possibly
have gotten, but clearly that's debatable.

The only thing I'd agree with is what Michael Hoffman said about posting
a snippet of your code instead of a zip file.

This is also debatable. I'd strongly recommend against
ever referencing a zip file in some other location when
posting requests for help, unless it's a very complex
situation and you have laid the groundwork for people
to be bothered going to all that effort. Even then,
there's at least one serious disadvantage... see below.

The benefits of posting a snippet are many, provided
we define an appropriate snippet to be "the smallest
piece of code that you can produce which reproduces
the problem and has the fewest external dependencies"
or some such:

1. The act of creating the above almost always leads
to the discovery of the problem and a solution, meaning
you don't even get to the posting stage.

2. Posting a snippet vastly increases the likelihood
someone (often many) will help, versus the chances when
you post a link to code elsewhere (which are near zero).

3. Posting a snippet means that the code is archived
along with the request, allowing people who follow
along later, perhaps with the same question, to reliably
find the code in question, and the fixed code in the
followups. Posting links to elsewhere makes it very
likely the code in question will have vanished, wasting
lots of time for those who come later.

4. It's just plain polite, good netiquette.

Caveat: posting monster programs is never a good idea,
and a good rule of thumb is probably that any snippet
posted (for any reason) in a mailing list or newsgroup
like this should be no more than about fifty lines
long. That should be enough to reproduce just about
any problem, if you aren't lazy...

-Peter