Other For new(er) members: How to post a question/issue

[KMatle]

1. Please post the code AND the error message from the logs as TEXT within CODE TAGS.
2. Don't post images
3. Describe what the problem is (full sentences, not 3 words, not "my car doesn't work - guess what it is")
4. Use the search function FIRST (assume you're not the first person having that question)
5. Assume that we have many power users here having huge and complex apps. B4x is working 100%. So if you have an issue it's mostly a programming mistake
6. Don't start complex projects without any experience
7. We love to help but you need to help us to understand the issue (see esp. 1 - 3)
8. Read the tutorials and manuals
9. Install B4x as described!
10. Have fun

Erel: 11. Always start a new thread for your question.

 

[Cableguy]

1. Please post the code AND the error message from the logs as TEXT within CODE TAGS.
2. Don't post images
3. Describe what the problem is (full sentences, not 3 words, not "my car doesn't work - guess what it is")
4. Use the search function FIRST (assume you're not the first person having that question)
5. Assume that we have many power users here having huge and complex apps. B4x is working 100%. So if you have an issue it's mostly a programming mistake
6. Don't start complex projects without any experience
7. We love to help but you need to help us to understand the issue (see esp. 1 - 3)
8. Read the tutorials and manuals
9. Install B4x as described!
10. Have fun

Small additions to your guidelines:

2. Don't post images - We mean, dont post images or screen captures of your logs and/or error messages!
App Screenshots or videos are fine, to exemplify a behaviour.

7. We love to help but you need to help us to understand the issue (see esp. 1 - 3) - We really do LOVE TO HELP, but Don't expect us to do the job for you! When you come across an issue, give us a starting point , a code sample, a stripped out project that we can take, analyse and POINT YOU IN THE RIGHT DIRECTION… we may even provide a fully working solution based in YOUR WORK IN PROGRESS!

8. Read the tutorials and manuals - Our Power(full) user @klaus has created a series of booklets that cover from the basics up to the complexes of B4X suite IDEs. YOU REALLY SHOULD READ THEM!

 

[DonManfred]

1. Please post the code AND the error message from the logs as TEXT within CODE TAGS.

This is how it works:

Please use [CODE]code here...[/CODE] tags when posting code.

 

[AnandGupta]

And still we will get posting from new members who will NOT follow the above

Regards,

Anand

 

[Erel]

Good points. I made it a sticky thread.

And still we will get posting from new members who will NOT follow the above

That is expected and is fine. It is important that new members will feel free to post in the forum.

 

[Computersmith64]

12: If someone is trying to help you & asks questions for clarification, don't ignore the questions.
13: Don't post the same questions in multiple different threads.

 

[LucaMs]

4. Use the search function FIRST (assume you're not the first person having that question)

Set it to 0 and sort again the list

 

[ronell]

14. after resolving the error/problem, post the solution if possible .. because sharing is caring

 

[udg]

because sharing is caring

sharing = caring --> car sharing?

Sorry, I couldn't resist.

 

[ronell]

sharing = caring --> car sharing?

 

[Mark Read]

14a. After posting the solution, mark the thread as [Solved] (change title). It helps others to see if a solution is there, especially with long posts.

I forget as well.

 

[Cableguy]

Humm maybe @klaus could add a "forum best pratices" chapter to his booklets!?

 

[klaus]

Done, for the next edition .

 

[Star-Dust]

7. We love to help but you need to help us to understand the issue (see esp. 1 - 3) - We really do LOVE TO HELP, but Don't expect us to do the job for you! When you come across an issue, give us a starting point , a code sample, a stripped out project that we can take, analyse and POINT YOU IN THE RIGHT DIRECTION… we may even provide a fully working solution based in YOUR WORK IN PROGRESS!

I fully subscribe to it.
Do not expect us to do the work for them instead of cavalry. Otherwise we should also collect the money agreed with the customer for them.

 

[Cableguy]

Done, for the next edition .

You, SIR, are just AMAZING!

 

[LucaMs]

Sometimes I think that a "how to answer" thread is also needed.

Answers like this one:

as far as i know, no.

are completely unusesul.

It is almost like:

Question: "How can I do...?"

and intervene for just to write: "I don't know"

 

[Erel]

are completely unusesul.

I don't agree. Especially when it comes from experienced members.

 

[LucaMs]

I don't agree.

I knew! Someone else will agree, I think.

 

[Erel]

As this thread has a very specific and important purpose I'm locking it.