Page 1 of 1

Problem with code window header

Posted: Mon Sep 23, 2013 10:12 am
by matgarage
Hi

I've got a problem with the code window.
When I make change on my code, I can validate by the Apply button.

But when an error block the code, I don't see the button in the top left of the window (triangle and square).

I think Livecode need some reseting to recover this button by I can find how to do that.


Could you help me ?

Re: Problem with code window header

Posted: Mon Sep 23, 2013 5:43 pm
by Traxgeek
Hi Matgarage,

I had the same 'problem' when I was starting out... It transpires that LC will not make this button available if there is a syntax (in fact, any) error in the window for the script you have been editing.

You need to fix the error -OR- temproarilly remark ( -- or # or /* ... */) out the offending line - usually hilighted by a red circle in the margin adjacent to the offending line, and itemised in the Errors tab at the bottom of the page.

NOTE : LC will only highlight the first error it comes across. This does not mean you only have one error, just that the highlighted one is the first one ! Fix it and you may well (well, I do) often have others just lurking with intent. LC deals with each one sequentially, until all errors in that script are rectified.

From time to time, I find myself simply remarking out the offendding line(s) to enable the 'Save' and then go back and fix my error(s) one at a time knowing my 'brainwave' is 'safe' - works for me ! :)

Personally, (I'm sure there is a very good reason for it, like it's LIVE code - and I stand to be corrected - but) I think the code should save anyway (with / without errors)... but then that's just me (I'm sure there is a very good reason for it behaving the way it does - just takes some getting used to !).

HTH.

Regards.

Re: Problem with code window header

Posted: Wed Sep 25, 2013 8:01 pm
by matgarage
Hi Traxgeek

Thank you for your response.
My problem was not about error in script.

I got a similar problem in the header of the dictionary.
I work on livecode at job for some simple tools and at home for fun.
At home : no problem with the display in window.
But the same version of LC and stack at job get the bug.

I will try to clean desinstal livecode and then re-instal it.


I will let you know the result.

Best.

Re: Problem with code window header

Posted: Wed Sep 25, 2013 10:37 pm
by dunbarx
There are runtime and compileTime errors.

CompileTime errors are like:

Code: Select all

on mouseUp
  answer XX "Hello"
This won't compile, because it uses an unlawful syntax, and the engine is telling you so. And why. Very important to know.

This is a runtime error

Code: Select all

on mouseUp
  answerXX "Hello"
This is fine with the engine as it stands, but it will fail when the script executes, and no "answerXX" handler is found anywhere. Sort of like trying to put data into a field that does not exist. There is no way for LC to know if either of these two instances are bad until the script is executed. Also very useful.

Craig Newman

Re: Problem with code window header

Posted: Fri Nov 15, 2013 10:27 am
by matgarage
Ok, I will try to illustrate my problem :
In the first screenshot you can see the code window where I've set a breakpoint in my code
Capture d’écran 2013-11-15 à 10.20.23.png
In the second screenshot, the same window after the script was triggered by mouse up
Capture d’écran 2013-11-15 à 10.20.49.png
You can ses that the script is well stopped at my breakpoint, but i can see the buttons to navigate in the script : Green triangle, Blue Square, Next Statement...

At home, all works fine, but here at my job, i get this display bug.

Is there someone to help me to resolve this problem ?

Re: Problem with code window header

Posted: Fri Nov 15, 2013 7:50 pm
by jacque
That's really odd. It looks like either LiveCode can't find the icon images, or the buttons have been deleted or hidden. There should also be a toggle arrow at the far right side of the window that shows/hides the buttons and other parts of the top toolbar. It should be just to the right of the "recent scripts" button.

If something has accidentally removed the buttons you should be able to get them back by reinstalling LiveCode.

Re: Problem with code window header

Posted: Sat Nov 16, 2013 10:38 pm
by matgarage
Hi jaque

I've tried to re-install, to upgrade, to remove RunRev folder in my library/application support/ folder... but nothing works.

At home on an old core duo imac on 10.6 it work fine. But at my job, on 2011 iMac with Lion, hum, you've seen ;-)

I've tried with a new session too, same result.

Re: Problem with code window header

Posted: Sat Nov 16, 2013 11:08 pm
by jacque
The LiveCode installer won't always replace your copy if it's the same version as the one on disk, so you need to completely remove it before reinstalling. Did you try deleting the application itself?

Then log into your RR store account and manually download a new copy of LiveCode. Install it from that file, and let us know if it works.

Re: Problem with code window header

Posted: Mon Nov 18, 2013 9:49 am
by matgarage
I've already tried that. I've redone it this morning but it's not working. It's very strange.

Re: Problem with code window header

Posted: Mon Nov 18, 2013 8:24 pm
by jacque
Sounds like a note to support is in order. I've honestly never seen anything like this, you may have discovered a new feature. :)

Send your images and an email to support@runrev.com. I'm curious what they have to say, if you get a chance to report back here.

Re: Problem with code window header

Posted: Sat Nov 23, 2013 11:37 am
by matgarage
Jaque

I've sent a mail to the Support,I will post response here.

Tank you

Re: Problem with code window header

Posted: Thu Nov 28, 2013 9:10 am
by matgarage
Ok, i've got an answer from the support.

The problem is a conflict between Livecode and PitStop (an extension of Acrobat).
The only solution is to delete PitStop or to keep the bug.

I need Pitstop for my job, so...

Thanks for your help

Re: Problem with code window header

Posted: Fri Nov 29, 2013 9:14 am
by jacque
Thanks for the info. I thought it might have been something like that. An issue that strange had to have an equally strange cause.