LiveCode 8

[lohill]

How can the "powers the be" talk about phasing out support for versions 6 and 7 and suggest that it is time to start using version 8. I have version 8 (dp 16) and tested with a copy of one of my projects. I tried to edit a line of script and the Apply button would not work. (The dot never went to green.) I was not able to save the script changes. I also had two crashes of the application within 5 minutes. In my opinion, abandon 8 as a wast of time and make 7 perfect.

Larry

[FourthWorld]

LC 8 is in development precisely to help identify and resolve such issues. Versions 6 and 7 remain supported with maintenance releases while bug reports are submitted and resolved for v8.

What are the report numbers for the issues you've submitted with v8?

[lohill]

ForthWorld,

I have filed bug reports but not on version 8. To cite one which has been confirmed but not yet solved take a look at bug #15917. It was confirmed on 9/18/15 and multiple releases of LC7 have been released since but with no solution. If they stop working on 7, I bet that never get solved because, for them, it is not a priority.

Larry

[FourthWorld]

If they stop working on 7, I bet that never get solved because, for them, it is not a priority.

That would only be true if the problem is specific to v7, and it it's limited to v7 it won't be a problem moving forward.

There's been much work on Prefs and more recently with fonts - do you know if this problem persists with the latest build of v8?

It would be worth testing it and posting a comment there with that info. If the problem is fixed you can close the report, and if not the info will help the team prioritize this for work moving forward.

[lohill]

I checked Version 8 db16 and this bug is also present there. I added that fact to my original report on Version 7.

Larry

[FourthWorld]

Thanks for updating the report, Larry. I've added myself to the CC list for that report, and answered the question you included there.

[lohill]

Richard,

This is interesting. As it turns out my problem with Version 8 may be due to the plugin that I put into my startup that tries to change font sizes for the various tools that LiveCode uses. In disabling that so I could test Version 8 as you suggested, I found that the simple things I was doing in 8 worked just fine and were not crashing. After reporting that v8 still did not honor my preferences, I reinstalled my plug in and discovered at least two lines in my plugin that would not work due to radical changes in revDictionary. The lines are shown below and refer to things that do not exist in revDictionary anymore. My workaround to the workaround is to check revAppVersion() and if the first character is "8" then go around those two lines. I'll do some more work in 8 now to see how things go.

Code: Select all

      set the dgProp["text size"] of  group "Grid" of card "Index" of stack "revdictionary" to lTextSize
      set the dgProp["row height"] of group "Grid" of card "Index" of stack "revdictionary" to lRowHeight

Larry

[lohill]

It appears that with the introduction of the Browser widget in version 8 that code like that shown below no longer works. Many of my apps use similar code that fail to creating a browser instance. Is this a bug that should be reported or am I required to adapt my applications to use the widget?

Code: Select all

on openCard
   --If there are any open browsers close them
   resetCard
   
   --Create a browser object
   lock messages
   --The lBrowserID will be used to reference the browser
   --in the in the App
   put revBrowserOpenCef(the windowId of this stack) into lBrowserID
   unlock messages
   
   if lBrowserID is not an integer then
      answer "Failed to open browser"
   else
      --This links or sets the rec area of the browser 
      --to the rec area of the "browserBackground"
      revBrowserSet lBrowserID,"rect",the rect of graphic "browserBackground" 
   end if
end openCard

[jacque]

The CEF browser had to be removed from LC 8 on OS X because "upstream support" was dropped. Change back to the older revBrowser and it should work. I believe revBrowserCEF still works on Windows.

[lohill]

Jacque,

I'm not sure what you mean by "upstream support" but does that mean I can now count on being able to use revBrowserOpenCEF on the PC side and the plain revBrowserOpen on the Mac side. It is critical for me to be able to use 'CEF' on the PC side because of the inability of Explorer to handle long URLs.

Larry

[jacque]

Jacque,

I'm not sure what you mean by "upstream support" but does that mean I can now count on being able to use revBrowserOpenCEF on the PC side and the plain revBrowserOpen on the Mac side.

That's my understanding, yes. "Upstream support" was the term LC used in the release notes, I assume it means that the library they depended on is now unsupported by the developer on OS X.