Yes, I think a setting for the default would be good. And Thanks!
- Log in to post comments
Yes, I think a setting for the default would be good. And Thanks!
+1 for mimicking any Atlassian behavior.
Also, I don't know if this is new since you posted but with the two WYSIWYG editors you can add images inline. However, I agree that a more elegant paste-to-attach solution would be super useful, much like Confluence or StackExchange uses.
Thanks for the introduction. I'm looking forward to annoying you providing lots of feedback!
Thanks John. The fact that a Director and VP have replied to this confirms to me the priority placed upon this product.
I can't wait to see where it goes.
Thanks!
Thanks for the quick reply. Can you provide any information on the team or individuals responsible for the community? Do they have other responsibilities?
Any thoughts on why simple, obvious things like the quality of the main banner image have not been fixed? Is there a set development cycle?
Sorry if I come across as rude, I'm just curious and want to help the site improve.
To add to this, here is fa-reply from the ubiquitous Font Awesome library:
![]()
And here is fa-share:
![]()
And here's a little google search for "icon reply" and one for "icon share" and "icon forward".
I'm glad I saw that post, now I know that the forward looking button is actually for replying :)
To be clear, by "index" I meant the community index.
I'm curious how this one even happened, it's especially confusing since Timothy is the one that is reporting it!
Me too. Good one!
Another note, UI ambiguities like this are less of an issue if you add simple tooltips.
Oh wow, so that's a "Reply" button? Honestly the arrow is pointing the wrong way. That's the standard for "Forward" and I assumed it was a share button. Please fix.
And just to elaborate a little, what I was trying to do involved a lookup table. Let's say I had an FTP adapter that picked up files from /ftpdir/ and 1 subfolder deep. If I had
/ftpdir/green/
/ftpdir/red/
I could then have entries in the lookup table for "green" and "red" and (relatively) easily create a rule to do stuff based on the folder. What I'm trying to do now is be able to block things. So I have a lookup table named "BlockCustomer". I could create the key value pair "green:1" and then use $PIECE on the proposed .SourcePath property to determine if it should be blocked.
Although now that I think about it, I guess this could be done with the message header. However if I have multiple facilities for a single customer the given field in the header may differ. I'm not sure.
If you think this is a valid request worth implementing I would think a dedicated property like .SourcePath that contains "/hl7/1/yellow" would be best to avoid as much string manipulation as possible.
I'd like to hear other opinions though.
I think using message header information is the obvious solution, but my reasons for doing this were slightly more complicated. No need to elaborate though as I think I'll end up writing a custom function.
Thanks for the input.
User Dmitry Maslennikov has stated on this StackOverflow question that it does include the full path but when I looked in the viewer it was visually truncated. I hadn't been able to verify in code yet.
I'll see if I can validate and if it's not there then use part of the message header.
Thank you again!
Perfect! Reminds me of Master Pages for older .NET applications. This is what I suspected but since I didn't know the term "pane" I couldn't search the documentation. Thank you!
Perhaps the docs I linked can be updated to reference the page on "panes"
This seems to happen on every form. Also, once you backspace all the content you cannot get the curser back in the editor without refreshing the page.
By the way it is working perfectly. Thank you.
So is the <form> required or can you specify the data controller some other way?
Looks like they removed this from all but the main index. But you're right, the quality of the photo is terrible.
Related: There is no feedback when you rate a post. I had to refresh the page before I was sure it even worked.