DesignNoIntialInfobox=1 ignored

  • I’ve been using DesignNoIntialInfobox=1 in notes.ini for years and years, so long that every single client install gets that put in very first thing, but R8.5 appears to ignore it. Every time I open an Agent I get that annoying innane properties box popping open, as if I change Agent properties every single editing session. That would be no.- Views exhibit this behaviour as well, but Forms and Script Libraries do not. If it’s going to have a default I’d prefer “no” across the board, not some elements hide a huge chunk of the screen for no purpose while others don’t.

  • If nothing else I would dearly love to see the ini setting honored once again, putting that choice back in the developer’s hands where it belongs.

  • The rest of this is just griping, as if this isn’t. (grin) Skip it at your leisure!

  • Thanks for your time…

  • While I’m griping about the properties box I’d like to once again suggest that this thing not FORCE itself to be on top of everything all the time. If it would just allow itself to be covered by other active panels then the fact that the freak keeps magically appearing wouldn’t be nearly so frustrating, because it wouldn’t hide a huge chunk of the very design element I’m attempting to edit. If it’s painted, but under everything, then bring it to the fore if I try to summon it again. Simple. Effective.

  • And while I’m griping about properties in general, the DDE/Xpages/whatever editor puts properties in a completely foreign and counter-intuitive place. The properties themselves look like plain-vanilla HTML controls the like of early 90’s web page design, and the antiquated controls don’t even “flow” to fit the width of the panel they are in, making even trivially simple editing require scrolling left and right, over and over. XPages are a very interesting thing, but interacting with them in DDE is so exceedingly uninteresting that I dread building an application using them.

  • I’d like to see DDE properties in their own panel, like everything in Eclipse, not some afterthought-looking inflexibly located webby mess. Then the developer would have control over how and where properties appear, which is exactly as it should be.