Text with title

[rob]

Originally Posted by Bidmaron

Folks, I gave them an easily workable solution in my previous post that does exactly what we want. We shouldn't settle for a half-assed solution. It is easy. You compute a field that is the concatenation of the label and the content and this is what is visible in view mode. In edit mode you hide that computed field and show the separate label and text fields. The only issue is that the display code would have to set like a word paragraph indent to start the first line past where the label ends. The code would have to redetermine the indent amount any time the dynamically-sized label is edited. The z order of the label would be maintained on top of the content field. This is not that hard to do. Don't settle for something less.

Your proposed solution fails to handle a number of nasty complexities that you're probably not considering. Those issues turn your "easy" solution into a decidedly more complicated task.

So here's a critical question to consider...

Would you rather have us do it sooner using a simpler solution that we can implement relatively quickly? Or do it your way and likely have it take months longer before it actually gets implemented because there are numerous other features of significantly higher priority?

Tasks that take less than a day can be slotted in between "big tasks", allowing us to get some of them done on a steady basis. Tasks that take multiple days get prioritized along with all other meaty tasks, which means they don't get tackled for a much longer time unless they are high priority.

If you take the attitude of "don't settle for less", then you're effectively saying you're happy to wait a potentially long time for a feature, as it has to be weighed and prioritized against everything else. That's just the reality of the situation, since there are hundreds of things on our todo list, all of which are screaming for attention, and we can only do a few at a time.

Please keep this reality in mind when making requests.

Also, given all the complexities inherent to Realm Works, declaring something as "easy" without a thorough analysis of the actual technical implications is "bad form" on so many levels - not to mention that it's utterly misleading to others. You may have an idea of how it MIGHT be easy to do, but that doesn't mean it IS easy until you've actually considered all the technical implications. As a techie yourself, I'm sure you've encountered such situations numerous times, and I'm disappointed you allowed yourself to fall into that trap here.

Offering suggestions is GREAT, but please don't make assumptions about what is or isn't easy from a technical standpoint with Realm Works. I'm sure you'd be quite surprised at some of the things that seem easy and are actually hard, as well as some of the things that seem hard and are actually easy.

Thanks!