{"id":275,"date":"2009-12-09T17:43:24","date_gmt":"2009-12-09T21:43:24","guid":{"rendered":"https:\/\/clarionsharp.com\/blog\/?p=275"},"modified":"2009-12-09T17:43:24","modified_gmt":"2009-12-09T21:43:24","slug":"release-update","status":"publish","type":"post","link":"https:\/\/clarionsharp.com\/blog\/release-update\/","title":{"rendered":"Release update"},"content":{"rendered":"<p>The day before Thanksgiving I posted about the upcoming release of 7.1 (and the next update for Clarion.Net), and I wrote that we expected to make it within 2 weeks.\u00a0 In that same post I mentioned we&#8217;d be closed for a long (for us) 4 day break over the holiday.\u00a0 Well it seems some people took that 2 weeks literally to mean 14 consecutive days, and not the next 2 <em>working<\/em> weeks. Ahem, even our developers take a day off now and then&#8230; \ud83d\ude42<\/p>\n<p>We are in final closedown for the 7.1 release, we planned to have it ready by this Friday (and that would be within the 2 working weeks!), but there is a chance it&#8217;ll have to go out on the following week. Why?\u00a0 Well there were a few &#8220;hot topics&#8221; brought to our attention last week and we decided to tackle 2 of them. So if you don&#8217;t get a notification of the 7.1 release this Friday, just relax over the weekend and look forward to getting 7.1 early next week. The same applies for the Clarion.Net release!<\/p>\n<p>Here is what we&#8217;ve been working on these last 2 weeks, and indeed some of these items did consume a bit of extra time (the first 2 items were the &#8220;hot topics&#8221; I was referring to)<\/p>\n<p>WORKAROUND: The OS could position some Menu items outside the screen boundary if there were sufficient number of items to cause a multi-column overflow<br \/>\nFEATURE: You can now set if the Copy Referenced Dlls to Output Directory defaults to On or Off via the Tools\/Options\/Clarion\/General tab<br \/>\nFEATURE: The PRIVATE attribute is now allowed for TYPE declarations<\/p>\n<p>CHANGE:\u00a0 Better error message when an included project cannot be found during a make<br \/>\nCHANGE:\u00a0 When you associate the C7 IDE with .app files, the .app files now get an appropriate icon displayed in Windows<br \/>\nCHANGE: FILEs declared within a Procedure are now Private data to that Procedure<br \/>\nCHANGE: Menu style now takes into account dimensions of particular item defined in MENU\/MENUBAR declaration or set at run time (in latter case PROP:NoWidth and\/or PROP:NoHeight must be set to FALSE)<br \/>\nCHANGE: Post a warning if window\/report parser changed some control definition because a variable used as a attribute&#8217;s parameter does not exist anymore<br \/>\nCHANGE: Warning if PRIVATE and PROTECTED are used incorrectly<br \/>\nCHANGE: private queue types in abfile.clw are now marked private to take advantage of the updated clw compiler and reduce the number of duplicate symbols possible<br \/>\nCHANGE: renamed internal class used in the Query control QEIPManager to QueryQEIPManager because it was duplicated with the public method with the same name.<\/p>\n<p>FIX:\u00a0 %ApplicationExternalLibrary was returning the wrong value if you edited the project properties of an app, but did not set the model (ie left it at the default value of dll)<br \/>\nFIX:\u00a0 An exception would be thrown by the data pad if you copied a field and then tried to paste it into an empty local data list<br \/>\nFIX:\u00a0 Not all compilers were registered if you created a new C6 version<br \/>\nFIX:\u00a0 The Data pad could throw an exception if you tried to add a Queue to local data<br \/>\nFIX: Aboop.tpw: Incorrect declaration of a variable for the return value was generated if the procedure return type in the prototype was ? or *?<br \/>\nFIX: Avoid auto-#RELEASE on emitting unconditional source lines<br \/>\nFIX: Setting of PROP:NoHeight and PROP:NoWidth properties for menu items worked not as documented.<br \/>\nFIX: Source Editor &#8211; Search\/Replace would fail for various conditions<br \/>\nFIX: The ISAM file imports would not work if you had a file with a . in the name.<\/p>\n<p>PTSS 32051: Suppress Windows internal repainting of the button upon changing its text<br \/>\nPTSS 33701: Clarioncl would some times fail to register templates if multiple \/tr switches where supplied on the command line<br \/>\nPTSS 33804: Lookup table must be updated first before record validation<br \/>\nPTSS 34190: GROUP and OPTION controls cannot be selected themselves but they provide defaults for selected text and background colors to nested controls<br \/>\nPTSS 34226: Current build configuration was not being passed so the %ApplicationDebug symbol was not setup correctly<br \/>\nPTSS 34563: Show warning if WINDOW with TOOLBOX\/DOCK\/DOCKED attributes has the MDI attribute too<br \/>\nPTSS 34600: Changing of variable name in the Data Pad was not reflected in changes to attributes of WINDOW\/REPORT controls using that variable as a parameter<br \/>\nPTSS 34605: The window previewer would not work with ENTRY controls that had @P or @K pictures<br \/>\nPTSS 34631: Designers might not be available in plain embed editor<br \/>\nPTSS 34643: Implementation of drawing of themed borders for RTF controls<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The day before Thanksgiving I posted about the upcoming release of 7.1 (and the next update for Clarion.Net), and I wrote that we expected to make it within 2 weeks.\u00a0 In that same post I mentioned we&#8217;d be closed for a long (for us) 4 day break over the holiday.\u00a0 Well it seems some people &hellip; <a href=\"https:\/\/clarionsharp.com\/blog\/release-update\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Release update<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,5],"tags":[],"class_list":["post-275","post","type-post","status-publish","format-standard","hentry","category-clarion-7","category-clarionnews"],"_links":{"self":[{"href":"https:\/\/clarionsharp.com\/blog\/wp-json\/wp\/v2\/posts\/275","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/clarionsharp.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/clarionsharp.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/clarionsharp.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/clarionsharp.com\/blog\/wp-json\/wp\/v2\/comments?post=275"}],"version-history":[{"count":0,"href":"https:\/\/clarionsharp.com\/blog\/wp-json\/wp\/v2\/posts\/275\/revisions"}],"wp:attachment":[{"href":"https:\/\/clarionsharp.com\/blog\/wp-json\/wp\/v2\/media?parent=275"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/clarionsharp.com\/blog\/wp-json\/wp\/v2\/categories?post=275"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/clarionsharp.com\/blog\/wp-json\/wp\/v2\/tags?post=275"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}