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. In that same post I mentioned we’d be closed for a long (for us) 4 day break over the holiday. Well it seems some people took that 2 weeks literally to mean 14 consecutive days, and not the next 2 working weeks. Ahem, even our developers take a day off now and then… 🙂
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’ll have to go out on the following week. Why? Well there were a few “hot topics” brought to our attention last week and we decided to tackle 2 of them. So if you don’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!
Here is what we’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 “hot topics” I was referring to)
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
FEATURE: You can now set if the Copy Referenced Dlls to Output Directory defaults to On or Off via the Tools/Options/Clarion/General tab
FEATURE: The PRIVATE attribute is now allowed for TYPE declarations
CHANGE: Better error message when an included project cannot be found during a make
CHANGE: When you associate the C7 IDE with .app files, the .app files now get an appropriate icon displayed in Windows
CHANGE: FILEs declared within a Procedure are now Private data to that Procedure
CHANGE: 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)
CHANGE: Post a warning if window/report parser changed some control definition because a variable used as a attribute’s parameter does not exist anymore
CHANGE: Warning if PRIVATE and PROTECTED are used incorrectly
CHANGE: 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
CHANGE: renamed internal class used in the Query control QEIPManager to QueryQEIPManager because it was duplicated with the public method with the same name.
FIX: %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)
FIX: 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
FIX: Not all compilers were registered if you created a new C6 version
FIX: The Data pad could throw an exception if you tried to add a Queue to local data
FIX: Aboop.tpw: Incorrect declaration of a variable for the return value was generated if the procedure return type in the prototype was ? or *?
FIX: Avoid auto-#RELEASE on emitting unconditional source lines
FIX: Setting of PROP:NoHeight and PROP:NoWidth properties for menu items worked not as documented.
FIX: Source Editor – Search/Replace would fail for various conditions
FIX: The ISAM file imports would not work if you had a file with a . in the name.
PTSS 32051: Suppress Windows internal repainting of the button upon changing its text
PTSS 33701: Clarioncl would some times fail to register templates if multiple /tr switches where supplied on the command line
PTSS 33804: Lookup table must be updated first before record validation
PTSS 34190: GROUP and OPTION controls cannot be selected themselves but they provide defaults for selected text and background colors to nested controls
PTSS 34226: Current build configuration was not being passed so the %ApplicationDebug symbol was not setup correctly
PTSS 34563: Show warning if WINDOW with TOOLBOX/DOCK/DOCKED attributes has the MDI attribute too
PTSS 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
PTSS 34605: The window previewer would not work with ENTRY controls that had @P or @K pictures
PTSS 34631: Designers might not be available in plain embed editor
PTSS 34643: Implementation of drawing of themed borders for RTF controls
Hi Robert,
Could we get an updated release schedule please? We all know how timelines slide on projects; but I am anxiously awaiting some of the fixes that have already went out in prelease form (I was not one of the fortunate few). I appreciate the amount of fixes coming in the next version, but I personally would have loved a few interm releases to get past some issues months ago.
Joe.
“CHANGE: FILEs declared within a Procedure are now Private data to that Procedure”
Hasn’t it always been like that ?
The linker has been improved in 7.1, in prior releases link order could mask duplicate symbol errors.
I’ll post about it and go into more detail.
Thank you, I love to read articles that are informative and beneficial in nature.
Maybe next time the duration could be posted in “working day” units? 2 “work weeks” (and the ‘work’ was not included) is sort of vague.
Maybe there won’t even be a ‘next time’?
I am starting to be interested in this again. From what I’ve read on the previous topic and on this, it seems SV has decided to assume back the avant garde position.
Lets see.
Thanks for reporting the “delay” and even more the reasons why. Its okay for me, and I really fell better when I get informed seriously and honestly. The problem is not so much to deliver on the point (we talk about software ) , waiting a few more days doesn’t matter.
But it hurts to be kept in a state of know-nothing-with-lots-of-rumours. I feel like being treat like a child, “You do not need to know!”.
So thanks for the heads up – I look forward to next week!
Wolfgang
A question please :
“CHANGE: FILEs declared within a Procedure are now Private data to that Procedure”
Does this means that the structure of an application where all the “small” tables (for example ALIAS tables or TEMP tables) are declared in the table schematic “others” of a SINGLE source procedure declared globaly to “let” all the app “see” those tables will be broken ?
(and require us to add each and every table in each and every procedure who uses them ? – when one procedure per module)
JP
No, it means that a FILE declared within the Data section of a Procedure is Private to that Procedure, it has no effect on the FILE code generated by our templates
Great ..
thanks very much for the feedback. it is greatly appreciated
kind regards
Ben