I think you signed a non-disclosure agreement saying you wouldn't do this. :-)
Bob On Jan 23, 2013, at 9:50 PM, Sumner, Walt wrote: > Rather than get any real work done this evening, I've been dutifully trying > to describe a bunch of issues with the property inspector in LC6.0 dp4 > through the quality control center. However, the last straw was the QCC > demanding in bold letters on a blood red background that "A value must be set > for the 'Desktop OS' field." when there was no such field on the preceding > form, try as I might to find it. And if that data is missing, why can't it > ask, "What is your desktop OS?" It's not like there are that many required > fields. And I had already recorded that info in my report. If anyone knows > where to enter my desktop OS, please let me know. I looked in a lot of places > in the QCC, didn't see it. > > So, here's my list of problems with the PI. If anyone knows how to circumvent > them, please share. Anyone who can get this to RunRev's attention please feel > free, I need to invest my time elsewhere at this point. And please, RunRev, > can the feedback loop be a little more gracious? > > <REPORT> > The LC 6.0 dp4 new property inspector is practically unusable for me in > multiple regards: > > 1. Any object selected with the pointer tool changes content of the new > property inspector, but I cannot use the pointer tool to browse or adjust > anything in the new property inspector, I just wind up selecting objects in > the inspector. So I try switching to the browse tool, and the new property > inspector immediately changes focus to inspect itself: stack > "idePropertyInspector". It seems to work to pointer-click an object in my > stack, pointer-click a field in the inspector, and then choose the browse > tool. The inspector then displays information about the last selected object > in my stack (even though that object is now deselected), and it is possible > to browse. > > 2. If it is closed, the new property inspector pops up with every object > selection using the pointer tool, and gets in front of the stack I am trying > to edit. In fact, if I point at an object in my stack so that the new > property inspector comes to the fore, and then go to the tools palette and > double click on a button, the newly created button will appear in the > property inspector, not my stack. This is extremely unexpected and > disconcerting, especially given how hard it is to get the inspector out of > the way for any length of time. Shouldn't it be acting more like a palette > and less like a stack in development? > > 3. I have not found a way to suppress the new property inspector: it appears, > in front of my stack, with any double click of the pointer tool, and with any > single click of the pointer tool if the inspector has been closed. If this is > going to be released, opting for the old property inspector needs to be an > setting, IMO. > > 4. On one occasion that I cannot reproduce yet, turning on suppress messages > and then clicking on an object caused a function call to > ideMessagesSuppress() to hang with an effective freeze of Livecode - > unresponsive to command-period, quit, escape, etc. I had to force-quit > LiveCode, although it was still "responsive" in the opinion of the Activity > Monitor. I often have freezes that appear related to browsing the > documentation or manipulating the new property inspector but that can be > escaped with control-period to abort some script. This was different. > > 5. A lot of the text settings in the new prop inspector change the settings > of all of the fields in the prop inspector, which is very effective visual > feedback, but I don't know that I want all of the labels and contents in the > new PI struck through just because I want the field in my stack to display > struck through text, for instance. > > These behaviors were not an issue for me with LC 6 dp1, the version I had > been using until today. > > There are still issues with forcing custom property saves after manual edits > of the old property inspector. > > Computer: > Model Name: MacBook Pro > Model Identifier: MacBookPro4,1 > Processor Name: Intel Core 2 Duo > Processor Speed: 2.4 GHz > Number Of Processors: 1 > Total Number Of Cores: 2 > L2 Cache: 3 MB > Memory: 2 GB > Bus Speed: 800 MHz > Boot ROM Version: MBP41.00C1.B03 > SMC Version (system): 1.27f3 > Serial Number (system): W8823..... > Hardware UUID: E39105FB-...... > Sudden Motion Sensor: > State: Enabled > > OSX 10.5.8 > </REPORT> > > </RANT> > > Thanks, > > Walt Sumner > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
