LiveCode Forums

All of a sudden, I cannot click on individual items in the Application Browser. I can still call up the Inspector from the menu and then use the arrow to navigate to other items but it certainly isn't as convenient.

I checked the Prefs without seeing anything, then deleted the Prefs file from the Library (I'm on Mac) but no change on restarting.

I'm downloading a new copy of 5.0.2 now and will re-install.

Perhaps in a related vein, I tried to take a snapshot of a group using the message box - copying and pasting the syntax from the dictionary - and got an error:
Message execution error:
Error description: value: error executing expression
Hint: export snapshot from (the rect of group "GPB") with effects to file "tester.jpg" as jpeg

Which is less than helpful to me.

Can anyone be of more help?

Thanks

Kelly

For the snapshot part since you're defining a rectangle you have to use the rectangle keyword.

export snapshot from rectangle (the rect of group "GPB") with effects to file "tester.jpg" as jpeg

That's what I tried the iteration before the one I posted. I copied the syntax right out of the dictionary, so I've got to believe that was right.

Anyway, the download is finished so I'll do the reinstall.

Kelly

Might try

export snapshot from group "GPB" with effects to file "tester.jpg" as jpeg

That actually works Sturgis - thanks.

A reinstall seems to have solved the other IDE issues.

Thanks

Kelly

I don't know if this was the original problem or not, but sometimes you can be in debugging mode and not notice (for example, you left a breakpoint in a script and forgot about it.) When the script breaks into the debugger, very little else is clickable. It will look like LiveCode is not responding. When that happens the first thing I do is check the open script editor to see if it's in debug mode.

That said, the app browser does respond even in debug mode, so something else may have happened.

Thanks Jacque. I know the issue that you're talking about, but I'm sure that it was something else because the re-install fixed it.

Glad to be working again,

Kelly