Welcome to the Axure forums!
The guidelines below help us to build a community that is rooted in kindness, collaboration, and mutual respect. Whether you’ve come to ask questions or to generously share what you know, join us in building a community where all people feel welcome and can participate.
The Axure forums are a place where Axure customers of all levels of expertise can come to have their questions answered by the Axure support staff and by other members of the community. While you’re participating in this community, we ask that you keep the following in mind:
If you’re here to get help, make it as easy as possible for others to help you.
Read the guide below on how to ask a question. If you need urgent assistance, contact Axure support directly at firstname.lastname@example.org.
If you’re here to help others, be patient and welcoming.
Our forum community includes members with a wide range of experience levels, both with Axure’s products and services and with the software industry at large. Be empathetic when answering questions you might consider basic.
Be kind and friendly.
When providing feedback, be clear and constructive. Avoid sarcasm and be careful with jokes — tone is hard to decipher online. If a situation makes it hard to be friendly, stop participating and move on.
No subtle put-downs or unfriendly language
Even if you don’t intend it, this can have a negative impact on others.
|You could Google this in 5 seconds.||Here's a link to a tutorial on Axure's support site that teaches what you're looking for. I hope this helps!|
|No one can help you if you don't post your RP file.||I'm having a hard time reproducing the issue you described. Could you share your RP file so I can see what you're seeing?|
|I came here for an answer, not a link to a tutorial.||Thanks for sharing that tutorial with me, but it doesn't teach quite what I'm trying to build. My needs are different in this way:|
|Did you even read my question?||Thanks for your response, but this doesn't fully address my question. Let me try to explain in more detail.|
No name-calling or personal attacks
Focus on the content, not the person. This includes terms that feel personal even when they’re applied to content (for example, “lazy”).
We don’t tolerate any language likely to offend or alienate people based on race, gender, sexual orientation, or religion — and those are just a few examples. When in doubt, just don’t.
This includes but isn’t limited to bullying, intimidation, vulgar language, direct or indirect threats, sexually suggestive remarks, patterns of inappropriate social contact, and sustained disruptions of discussion.
Posts clearly intended to do nothing more than direct readers to third-party websites, products, or services will be deleted without question, and the posting account will be banned.
Every person contributes to building a kind, respectful community. If you find unacceptable behavior directed at yourself or others, you can report it by expanding the menu below the post and clicking .
You can also contact the Axure staff directly by emailing us at email@example.com.
We take your reports seriously. Those who don’t follow these guidelines in good faith may face repercussions deemed appropriate by our moderation team.
Every topic on the Axure forums should clearly ask a question related to working with Axure’s products and services. Follow the guidelines below to give the community the best chance to answer your question quickly and thoroughly.
Note: If you’re looking to submit feedback or make feature requests for Axure’s products and services, please contact us directly at firstname.lastname@example.org rather than posting on the forums.
Before posting a new question on the forums, take a look through the Support section of our website to see if there’s an answer in our documentation or tutorials. It’s also a good idea to search the forums to see if your question has already been answered in an existing topic.
Even if you don’t find what you’re looking for, it can be helpful to let the community know which solutions you’ve already explored. Knowing what didn’t solve the problem can help to identify what will.
Write a title that summarizes your question.
Providing a clear, informative title helps the community to quickly understand the problem you’re trying to solve. This is helpful both to members with potential answers for your question and to members who may be experiencing a problem similar to your own.
Use the following tips to craft a strong title:
Write your title last. Sometimes writing the rest of the post first can make it easier to succinctly summarize the problem.
Pretend you’re talking to a busy colleague and have to sum up your question in one sentence.
Include any error messages you’re seeing.
Describe any special contexts or unusual circumstances that make your question different from similar questions on the forums.
|Repeater help||How do you apply multiple filters to a repeater at once?|
|Font problem||Why does my custom web font get displayed as Times New Roman when I view my prototype on my iPhone?|
|Error when publishing||I get this error message when I publish to Axure Share from my new computer: "Unable to connect. Please make sure you have an internet connection and try again."|
|Text field bug||Hint text on text fields is treated as regular text in Google Chrome on Android devices.|
Make it easy for others to reproduce your problem.
The best thing you can do to help the community answer your question is to provide all the information necessary to reproduce the problem you’re experiencing. Whenever applicable, include the following in your posts:
a clear list of numbered steps to reproduce the problem
a copy of the RP file you’re working in or a stripped-down example file that includes only the relevant pages and widgets
screenshots and/or a video of the issue
information about your environment:
- Axure RP’s version and build number, available at Help > Check for Updates
- your operating system
- your web browser (if applicable)
Note: If you’re unable to share any of the above information on the public forums, email us instead at email@example.com.