Data Access Worldwide Knowledge Base
Article ID 2043 Article Title INFO: Save Component message when Resizing Components in 9.1and 10.0 Article URL http://www.dataaccess.com/kbasepublic/kbprint.asp?ArticleID=2043 KBase Category VDF9 Date Created 09/24/2004 Last Edit Date 09/24/2004
Article Text
QUESTION:
When maximizing a component, I am getting lots of messages telling me I've made changes to the component (view, application, etc.) in the Studio when I haven't. It's very annoying and this did not happen in 9.0. Why does this happen in 9.1?
ANSWER:
In Visual DatFlex 9.1 and 10.0, the Studio window size for each component is stored in the component's source code. By window size we mean the Studio window in which the component resides. Every time you resize this window, even if you maximize it or un-maximize it, it causes a change to that component, because the new window size has changed.
It is a change for the better, though, since you can now decide on a component-by-component basis how large you want the outer window for that component to be. For applications, for example, you can drop objects like cApplication objects into the window outside of the actual Main panel object, in which case you may want to resize the
window so you can adjust objects like these.
This has now changed in Visual DatFlex 10.1: the window size is still saved per component but it is saved to a separate file, not to the source code of the component. The "<component name> has been changed - Do you want to save?" message will no longer be triggered when you resize the Studio window size.
Contributed By:
Dennis Piccioni
Company: Data Access Worldwide
email: dennis@dataaccess.com
Web Site: http://www.dataaccess.com
Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2010 Data Access Corporation. All rights reserved.
The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.