Re: Palette command problem

[Kay C Lan]

On Fri, May 20, 2016 at 10:56 PM, J. Landman Gay
 wrote:
> Richard explained it pretty well.  I think of the command form as a
> temporary override.

Yes he did and that's a nice summary. Thanks.

___
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: Palette command problem

[Richard Gaskin]

J. Landman Gay wrote:

> I think of the command form as a temporary override. The bug here
> seems to be that the command fails on Linux.

After Fraser's excellent work on the Linux engine, the palette command 
seems to be working well - most of the time.


I have found a very few odd edge cases where it doesn't.  The team can't 
yet reproduce my latest:



If any of you have had issues you can reproduce with palettes, if 
they're related to revTools please add your noted to that report, and if 
related to any other stack please file a new report and note the report 
ID number here.  Thanks!


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.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: Palette command problem

[J. Landman Gay]

Richard explained it pretty well.  I think of the command form as a 
temporary override. The bug here seems to be that the command fails on Linux.


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



On May 20, 2016 3:06:37 AM Kay C Lan  wrote:


And as a further test - on OSX 10.9.5 LC 8.0.1 rc 1

New default stack
In message box:
palette stack "Untitled 1" -- works fine
put the style of stack "Untitled 1"
result: toplevel

Seems to be a bug.

___
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: Palette command problem

[RM]

If I put 'palette "XYZ"' in the messageBOx I get a palette.

If I put 'palette "XYZ"' in a stack called "XYZ" insode, say, a mouseUp 
message, I DON'T get a palette.


Richmond.

On 20.05.2016 17:23, Richard Gaskin wrote:

Kay C Lan wrote:

> Here on OSX 10.9.5 LC 8.0.1 rc 1 if I open a 'topLevel' stack and in
> the message box:
>
>palette stack "guineapig"
>
> the stack is palettised. But if I put this in the message box:
>
>put the style of stack "guineapig"
>
> the result is: topLevel ??
>
> If I revert the stack back to topLevel and in the message box:
>
>set the style of stack "guineapig" to palette
>
> it works, and if I then:
>
> put the style of stack "guineapig"
>
> the result is: palette
>
> Something definitely not right. Anyone else seeing the command
>
>palette stack "yourNameHere"

This all seems fine, given the unique roles of style and mode.

The style property is persistent, saved with the stack.  It's toplevel 
by default, but can be changed to modeless, modal, or palette.  When a 
stack is opened without specifying a mode name (as with "go" or 
"open") the stack will be opened in the mode determined by its style 
property.


At any time we can override the stack's style property by using a 
style name as a command, such as palette, modeless, etc. e.g.:


  palette "SomeStack"

Using a style name as a command will open the stack in the specified 
mode, but will not alter the persistent "style" property.  This is 
especially useful for things like palettes, so you can simply open 
them with "open" and when you want to work on them you can use the 
"toplevel" style name as a command:


  toplevel "SomeStack"

To determine the actual mode in use by a stack at any given time, use 
the stack's mode property.  This is determined at runtime and is 
read-only, an integer reflecting any of the various states a stack can 
be in.  Style names are not used here as the mode property covers a 
broader range of circumstances than a stack's style property, 
including a toplevel stack that has its cantModify set to true (2) as 
opposed to editable (1), or closed but still in memory (0).  Palettes 
will have a mode of 4.


It may be helpful to have mode listed among the See Also tokens in the 
Dictionary entry for the Style property.





___
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: Palette command problem

[Richard Gaskin]

Kay C Lan wrote:

> Here on OSX 10.9.5 LC 8.0.1 rc 1 if I open a 'topLevel' stack and in
> the message box:
>
>palette stack "guineapig"
>
> the stack is palettised. But if I put this in the message box:
>
>put the style of stack "guineapig"
>
> the result is: topLevel ??
>
> If I revert the stack back to topLevel and in the message box:
>
>set the style of stack "guineapig" to palette
>
> it works, and if I then:
>
> put the style of stack "guineapig"
>
> the result is: palette
>
> Something definitely not right. Anyone else seeing the command
>
>palette stack "yourNameHere"

This all seems fine, given the unique roles of style and mode.

The style property is persistent, saved with the stack.  It's toplevel 
by default, but can be changed to modeless, modal, or palette.  When a 
stack is opened without specifying a mode name (as with "go" or "open") 
the stack will be opened in the mode determined by its style property.


At any time we can override the stack's style property by using a style 
name as a command, such as palette, modeless, etc. e.g.:


  palette "SomeStack"

Using a style name as a command will open the stack in the specified 
mode, but will not alter the persistent "style" property.  This is 
especially useful for things like palettes, so you can simply open them 
with "open" and when you want to work on them you can use the "toplevel" 
style name as a command:


  toplevel "SomeStack"

To determine the actual mode in use by a stack at any given time, use 
the stack's mode property.  This is determined at runtime and is 
read-only, an integer reflecting any of the various states a stack can 
be in.  Style names are not used here as the mode property covers a 
broader range of circumstances than a stack's style property, including 
a toplevel stack that has its cantModify set to true (2) as opposed to 
editable (1), or closed but still in memory (0).  Palettes will have a 
mode of 4.


It may be helpful to have mode listed among the See Also tokens in the 
Dictionary entry for the Style property.


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.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: Palette command problem

[Paul Dupuis]

On 5/20/2016 4:08 AM, Kay C Lan wrote:
> If anyone else can confirm what Richmond is seeing or what I'm seeing
> I can raise a bug report.
>
 Same thing in LC8.0.0 under Windows 8.1

palette stack "Untitled 1" -- works fine
put the style of stack "Untitled 1"
result: toplevel

However, put the mode of stack "Untitled 1" returns the correct value
for a palette (i.e. 4)

___
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: Palette command problem

[Kay C Lan]

If anyone else can confirm what Richmond is seeing or what I'm seeing
I can raise a bug report.

___
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: Palette command problem

[Kay C Lan]

And as a further test - on OSX 10.9.5 LC 8.0.1 rc 1

New default stack
In message box:
palette stack "Untitled 1" -- works fine
put the style of stack "Untitled 1"
result: toplevel

Seems to be a bug.

___
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: Palette command problem

[Kay C Lan]

Interesting!

The example in the Dictionary Entry for 'palette' is:

palette stack "Tools"

so there is no reason why Richmond's original code should not work.

Here on OSX 10.9.5 LC 8.0.1 rc 1 if I open a 'topLevel' stack and in
the message box:

palette stack "guineapig"

the stack is palettised. But if I put this in the message box:

put the style of stack "guineapig"

the result is: topLevel ??

If I revert the stack back to topLevel and in the message box:

set the style of stack "guineapig" to palette

it works, and if I then:

put the style of stack "guineapig"

the result is: palette

Something definitely not right. Anyone else seeing the command

palette stack "yourNameHere"

not working as Richmond is experiencing on Linux?? (I assume). Or have
it work but not reported correctly when you:

put the style of stack "yourNameHere"

Richmond, can you get the 'palette' command to work from the message
box or elsewhere?

___
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: Palette command problem

[RM]

Yes, it does: thanks a lot.

Richmond.

On 20.05.2016 02:08, panagiotis merakos wrote:

set the style of stack "newTools" to palette



___
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: Palette command problem

[panagiotis merakos]

Hi Richmond,

Does [set the style of stack "newTools" to palette] work?
On 19 May 2016 22:29, "RM"  wrote:

> So, I have this command in the stackScript of a stack:
>
> on openStack
>   palette stack "newTools"
> end openStack
>
> and the stack is not becoming a palette.
>
> I'm obviously missing something.
>
> Richmond.
>
> ___
> 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

Palette command problem

[RM]

So, I have this command in the stackScript of a stack:

on openStack
  palette stack "newTools"
end openStack

and the stack is not becoming a palette.

I'm obviously missing something.

Richmond.

___
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