Support Board
Date/Time: Sun, 15 Jun 2025 16:51:19 +0000
Post From: TPO Study and Chart Drawing Alert
| [2025-06-09 19:23:38] |
| User173763 - Posts: 10 |
|
Hi Sierra Chart Team, Thank you for your answer. (Notice the greeting—common in human interaction and reflects a basic level of politeness.) I genuinely value your time and the effort it takes to respond to user questions. (Notice that I’m not being dismissive, nor do I assume my time is more valuable than others’. That said, your response gives the impression that less than 10 seconds were spent formulating it.) Now, to the core issue: To my knowledge, there is no mention in the documentation that the CROSSING alert condition is unsupported for chart drawings when used in conjunction with TPO charts. As a result, when this condition fails—while ABOVE and BELOW work as expected—it creates a lack of clarity in both the platform’s behavior and its documentation. Without knowing the root cause of this inconsistency, it becomes impossible to determine whether similar undocumented or buggy behavior may be present elsewhere in the system. (Notice the structured framing of the issue—coming from a long-standing IT professional background where clarity and transparency in system behavior are fundamental to diagnosing and resolving technical problems.) I do understand that it currently doesn’t work. (Notice I maintain a respectful tone, even though the phrasing “it just doesn’t work” sounds less like a professional technical response and more like something you’d hear from a teenager explaining why the Xbox won’t turn on after spilling Coke on it. If you are, in fact, a teenager helping out at the support desk this summer—my apologies. Please take this as a recommendation: in professional environments, we explain rather than evade. That’s how credibility and user confidence are built—especially when software behaves in undocumented or inconsistent ways.) I’m asking that you spend some time looking into this further—not out of entitlement, but because understanding the why is critical to ensuring reliable and predictable use of the platform. Inconsistencies like this deserve technical acknowledgment and, ideally, documentation—whether they’re design limitations or oversights—so users don’t waste time chasing behavior that can’t be reproduced or explained. Best regards, Leonidas |