Re: [ANN] Release 9.0.3 RC-1

[Terry Judd via use-livecode]

FWIW I've seen similar issues to this going back a while (I'm on MacOS but not 
sure what LC versions were involved). No recipe that I could find but 
restarting LC generally got things moving again.

Terry...

On 26/2/19, 1:19 pm, "use-livecode on behalf of J. Landman Gay via 
use-livecode"  wrote:

Just an update. I relaunched and have been working fine in 9.0.3 for 
several hours now. I'm at a loss to explain it.

On 2/25/19 1:43 PM, J. Landman Gay via use-livecode wrote:
> On 2/21/19 8:00 AM, panagiotis merakos via use-livecode wrote:
>> We are pleased to announce the release of LiveCode 9.0.3 RC-1.
> 
> I was hoping the strange problems would diminish with this release but I 
> lasted about 5 minutes before I had to quit and return to an earlier 
> version. I'm not sure how anyone can trace this, but thought I'd just 
> post what the circumstances were. Maybe someone will find a commonality 
> in their experience.
> 
> I'm working on a splash app that opens a separate mainstack, call it 
> StackA. The script of the app stack is inserted into the back. I was 
> debugging a handler on a card in StackA. The script editor was open and 
> a red-dot breakpoint was set.
> 
> I called the handler from the message box. -> Can't find handler
> The message box indicated that StackA was the target stack, and typing 
> "the defaultstack" in the message box also returned "StackA"
> 
> Repeated the message box call. -> Can't find handler.
> 
> Used the keyboard shortcut to summon the contextual menu and send the 
> handler name's message to the card. -> Works. Handler runs. Stops at 
> breakpoint.
> 
> I immediately saw a problem and aborted the handler in the middle. Made 
> some corrections and applied the script.
> 
> Called the handler from the message box. -> Can't find handler.
> Tried the contextual menu -> No response, no menu
> Tried "edit script of this cd" -> No response
> Tried "edit script of this cd of stack "StackA" -> no response
> Use keyboard shortcut to switch to Edit tool -> no response
> Tried clicking the Edit tool on the palette -> hilites, returns to 
> browse tool
> Repeated Edit tool selection from tools palette -> hilites, returns to 
> browse tool, but now I see it actually did choose the edit tool. I see 
> arrow-with-cross cursor.
> Double-click a field just to test -> no response
> Type in msg box: there is a fld "blah" -> true
> Use Application Browser to get the field property inspector -> works
> Click the Script button in property inspector -> no response
> 
> At this point I know I'm a hair's breadth away from a crash, so I quit 
> and return to LC 9.0.2 where this happens frequently but not quite as 
soon.
> 
> Anyone have anything in common with this sequence? I don't know what 
> triggers it, but the symptoms are usually the same: loss of keyboard 
> control, inability to find the current stack or card (although the 
> message box knows what it is,) inability to select or edit objects 
> except via Application Browser, and eventually a crash if you persist 
> long enough.
> 


-- 
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [ANN] Release 9.0.3 RC-1

[J. Landman Gay via use-livecode]

Just an update. I relaunched and have been working fine in 9.0.3 for 
several hours now. I'm at a loss to explain it.


On 2/25/19 1:43 PM, J. Landman Gay via use-livecode wrote:

On 2/21/19 8:00 AM, panagiotis merakos via use-livecode wrote:

We are pleased to announce the release of LiveCode 9.0.3 RC-1.


I was hoping the strange problems would diminish with this release but I 
lasted about 5 minutes before I had to quit and return to an earlier 
version. I'm not sure how anyone can trace this, but thought I'd just 
post what the circumstances were. Maybe someone will find a commonality 
in their experience.


I'm working on a splash app that opens a separate mainstack, call it 
StackA. The script of the app stack is inserted into the back. I was 
debugging a handler on a card in StackA. The script editor was open and 
a red-dot breakpoint was set.


I called the handler from the message box. -> Can't find handler
The message box indicated that StackA was the target stack, and typing 
"the defaultstack" in the message box also returned "StackA"


Repeated the message box call. -> Can't find handler.

Used the keyboard shortcut to summon the contextual menu and send the 
handler name's message to the card. -> Works. Handler runs. Stops at 
breakpoint.


I immediately saw a problem and aborted the handler in the middle. Made 
some corrections and applied the script.


Called the handler from the message box. -> Can't find handler.
Tried the contextual menu -> No response, no menu
Tried "edit script of this cd" -> No response
Tried "edit script of this cd of stack "StackA" -> no response
Use keyboard shortcut to switch to Edit tool -> no response
Tried clicking the Edit tool on the palette -> hilites, returns to 
browse tool
Repeated Edit tool selection from tools palette -> hilites, returns to 
browse tool, but now I see it actually did choose the edit tool. I see 
arrow-with-cross cursor.

Double-click a field just to test -> no response
Type in msg box: there is a fld "blah" -> true
Use Application Browser to get the field property inspector -> works
Click the Script button in property inspector -> no response

At this point I know I'm a hair's breadth away from a crash, so I quit 
and return to LC 9.0.2 where this happens frequently but not quite as soon.


Anyone have anything in common with this sequence? I don't know what 
triggers it, but the symptoms are usually the same: loss of keyboard 
control, inability to find the current stack or card (although the 
message box knows what it is,) inability to select or edit objects 
except via Application Browser, and eventually a crash if you persist 
long enough.





--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [ANN] Release 9.0.3 RC-1

[J. Landman Gay via use-livecode]

On 2/21/19 8:00 AM, panagiotis merakos via use-livecode wrote:

We are pleased to announce the release of LiveCode 9.0.3 RC-1.


I was hoping the strange problems would diminish with this release but I 
lasted about 5 minutes before I had to quit and return to an earlier 
version. I'm not sure how anyone can trace this, but thought I'd just 
post what the circumstances were. Maybe someone will find a commonality 
in their experience.


I'm working on a splash app that opens a separate mainstack, call it 
StackA. The script of the app stack is inserted into the back. I was 
debugging a handler on a card in StackA. The script editor was open and 
a red-dot breakpoint was set.


I called the handler from the message box. -> Can't find handler
The message box indicated that StackA was the target stack, and typing 
"the defaultstack" in the message box also returned "StackA"


Repeated the message box call. -> Can't find handler.

Used the keyboard shortcut to summon the contextual menu and send the 
handler name's message to the card. -> Works. Handler runs. Stops at 
breakpoint.


I immediately saw a problem and aborted the handler in the middle. Made 
some corrections and applied the script.


Called the handler from the message box. -> Can't find handler.
Tried the contextual menu -> No response, no menu
Tried "edit script of this cd" -> No response
Tried "edit script of this cd of stack "StackA" -> no response
Use keyboard shortcut to switch to Edit tool -> no response
Tried clicking the Edit tool on the palette -> hilites, returns to 
browse tool
Repeated Edit tool selection from tools palette -> hilites, returns to 
browse tool, but now I see it actually did choose the edit tool. I see 
arrow-with-cross cursor.

Double-click a field just to test -> no response
Type in msg box: there is a fld "blah" -> true
Use Application Browser to get the field property inspector -> works
Click the Script button in property inspector -> no response

At this point I know I'm a hair's breadth away from a crash, so I quit 
and return to LC 9.0.2 where this happens frequently but not quite as soon.


Anyone have anything in common with this sequence? I don't know what 
triggers it, but the symptoms are usually the same: loss of keyboard 
control, inability to find the current stack or card (although the 
message box knows what it is,) inability to select or edit objects 
except via Application Browser, and eventually a crash if you persist 
long enough.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [Solved] Colorizing line only works once?

[JJS via use-livecode]

Thanks GUys.


Yes it was probably something with sorting.

Strange also was that after a few times another row got red then the one 
which was hilited. So i don't know why.


Yes i use the "of me" whenever the script is in the dg itself. But 
sometimes i need to command it from outside the dg.


I removed what i was working on as it costed me too much time, and did 
the other option, as i mentioned in another post.


So now the background of a ceel of a column is turning red, which is 
even nicer as it draws more attention.



So thanks for your suggestions!

Regards,

Jerry


Op 25-2-2019 om 17:25 schreef Bob Sneidar via use-livecode:

On Feb 25, 2019, at 08:03 , Tom Glod via use-livecode 
 wrote:

   - dgline and dgindex are different, and as bob said, when the sort is
   on, you have to work with dglines.

Yes, lines will reorder according to their visible order, indexes will maintain 
their values persistent through a sort.

This is a mixed blessing. Let's say you get the dgHilitedLine of a datagrid, 
then wait for the user to do something with the data. In the interim the user 
resorts the datagrid! Now when you go to SET the dgHilitedLine, it's no longer 
the same data!

I always use dgHilitedIndex for this reason. The only reason you need 
dgHilitedLine is when you MUST process the data in the visible order. For 
instance if I delete a row, and I want to automatically hilite the prior row, I 
need to use the dgHilitedLine -1.


   - remember to use the "of me" syntax with every change you make to the
   controls of each row

As mentioned in another recent post, "of me" is necessary because each line of 
a datagrid has a set of controls for each row named the same as every other row. While 
this is allowed in Livecode (I never understood why) it means that referencing a specific 
copy of a control requires you also reference the row group it belongs to. I suspect 
these messages get sent to the row group specifically so that LC can reference the 
specific control for a given row.

Bob S


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Colorizing line only works once?

[Bob Sneidar via use-livecode]

> On Feb 25, 2019, at 08:03 , Tom Glod via use-livecode 
>  wrote:
> 
>   - dgline and dgindex are different, and as bob said, when the sort is
>   on, you have to work with dglines.

Yes, lines will reorder according to their visible order, indexes will maintain 
their values persistent through a sort. 

This is a mixed blessing. Let's say you get the dgHilitedLine of a datagrid, 
then wait for the user to do something with the data. In the interim the user 
resorts the datagrid! Now when you go to SET the dgHilitedLine, it's no longer 
the same data! 

I always use dgHilitedIndex for this reason. The only reason you need 
dgHilitedLine is when you MUST process the data in the visible order. For 
instance if I delete a row, and I want to automatically hilite the prior row, I 
need to use the dgHilitedLine -1. 

>   - remember to use the "of me" syntax with every change you make to the
>   controls of each row

As mentioned in another recent post, "of me" is necessary because each line of 
a datagrid has a set of controls for each row named the same as every other 
row. While this is allowed in Livecode (I never understood why) it means that 
referencing a specific copy of a control requires you also reference the row 
group it belongs to. I suspect these messages get sent to the row group 
specifically so that LC can reference the specific control for a given row. 

Bob S


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Colorizing line only works once?

[Tom Glod via use-livecode]

i have no idea why this is happening, but I do a lot of work with data
gridsand the rows in a grid are self referenced, so its unlikely to be
a bug in the grid.


   - dgline and dgindex are different, and as bob said, when the sort is
   on, you have to work with dglines.
   - rows are cached and must be refreshed (make sure you set the controls
   of each row and not assume that the default row state is what will show up)
   - remember to use the "of me" syntax with every change you make to the
   controls of each row


It is likely to turn out a bug in your code .. so thats the good part.

Good luck, let us know

On Mon, Feb 25, 2019 at 10:43 AM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:

> If the datagrid is sorted differently than the order the data is in, you
> may get that. I ran into this in the past I think.
>
> Bob S
>
>
> > On Feb 24, 2019, at 03:46 , JJS via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Just did some tests. with the test stack from the lesson and with my own
> stack
> >
> > It seems there is something strange with my indexes.
> >
> > I would think that if a DG is emptied and then filled again that the
> index would start at 0 or 1 again.
> >
> > It seems not the case and i see random numbers
> >
> > so i have to figure out why this is happening
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Colorizing line only works once?

[Bob Sneidar via use-livecode]

If the datagrid is sorted differently than the order the data is in, you may 
get that. I ran into this in the past I think. 

Bob S


> On Feb 24, 2019, at 03:46 , JJS via use-livecode 
>  wrote:
> 
> Just did some tests. with the test stack from the lesson and with my own stack
> 
> It seems there is something strange with my indexes.
> 
> I would think that if a DG is emptied and then filled again that the index 
> would start at 0 or 1 again.
> 
> It seems not the case and i see random numbers
> 
> so i have to figure out why this is happening


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

[ANN] This Week in LiveCode 169

[panagiotis merakos via use-livecode]

Hi all,

Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!

Read issue #169 here: https://goo.gl/oZDKgj

This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around the open source project. New issues will be
released weekly on Mondays. We have a dedicated mailing list that will
deliver each issue directly to you e-mail, so you don't miss any!

If you have anything you'd like mentioned (a project, a discussion
somewhere, an upcoming event) then please get in touch.


-- 
Panagiotis Merakos 
LiveCode Software Developer

Everyone Can Create Apps 
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

LC 9.0.2 and HTML5

[Alain Vezina via use-livecode]

Hi all,

I tested one of my applications with Safari 12.0 and when it loaded an HTML 
page i received this message :

err #3
enlarged memory arrays from 67108864 to 134217728, took 87 ms (has 
ArrayBuffer.transfer? false)

This application works very well on OS 10.12.6, on iOS 10.3.3 and on Android

What can I do to fix this problem?
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Colorizing line only works once?

[Sphere via use-livecode]

Solved it another way which also perfectly fits the idea by following 
this:

https://forums.livecode.com/viewtopic.php?t=13025#p62226
Thanks to Sri.


JJS via use-livecode schreef op 2019-02-24 11:46:
Just did some tests. with the test stack from the lesson and with my 
own stack


It seems there is something strange with my indexes.

I would think that if a DG is emptied and then filled again that the
index would start at 0 or 1 again.

It seems not the case and i see random numbers

so i have to figure out why this is happening


Op 23-2-2019 om 19:09 schreef JJS via use-livecode:

Hello,


i used this lesson: 
http://lessons.livecode.com/m/datagrid/l/7332-how-can-i-colorize-individual-lines-in-a-table


to colorize a few lines in my DG. When in one column the value is 1 
then the line stays black, when it is a 2 the line becomes red.


Now it just works :)...but only 1 time.


After repopulating the DG with stuff from an other category it does 
not do it although the same sequence is being done.


It only does it again when i reload the stack in the IDE.


Any idea what i can do?

Refresh index or line does not help


Thanks for any help.


Jerry


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode