Maximize to fit screen.

[boqsc]

Why do the stack only maximize by half of the screen? (The height of the stack is much lower than my screen, but the max-height of the stack is much bigger (6666)) Is there any way to make full sized maximization?

[dunbarx]

Hi,

Can you set the rect of your stack to the screenRect?

Craig Newman

[boqsc]

Hi,

Can you set the rect of your stack to the screenRect?

Craig Newman

Thanx for answer, but its realy not what i need.
i need fully maximize stack, when i press maximize button in the title bar. What i get, when i press instead of it, you can see above.

I think i need a handler witch will help me to do it. I searched everywhere and realy can't find way to do this.

Still looking for solution after 2 weeks.

[dunbarx]

No. I meant literally:

set the rect of this stack to the screenRect

Try it in a button or in msg.

Craig

[Simon]

No. I meant literally:

I'm still laughing!!!
That is going to make me smile all day.

Simon

[boqsc]

As i said, it's not what i'm looking for.

Look, all i want to do is just make stack fit screen after i press maximize button witch is in the title bar by not hiding the title bar of the stack.

The maximize button in the tool bar i'm talking about: Attachment [The maximize button of the stack.]
By the way, i tried to set the rect of this stack to the screenRect, it's working, but not that way i want.

[Simon]

Hi boqsc,
Are you using dual monitors?

Simon

[boqsc]

Hi boqsc,
Are you using dual monitors?

Simon

No, i'm using laptop with resolution: 1366x768
Is this problem only with the low-resolution monitors or something, it looks like it's old bug of the livecode how i read before and it's still not fixed if i'm right.
I'm searching for the solution silently for two weeks, but all i found is: nothing. And it seems almost noone mentioned ths problem before. Everyone is happy about the way the livecode resize stack?

Even defaults/originals livecode stacks didn't resize correctly.

[dunbarx]

Ah,

Now I see what you mean by "not the way I want". It is how it is done, not, er, how it is done.

i don't think there is a message sent when the maximize button is pressed, but there is a message "resizeStack", that is sent when the stack is, er, resized.

So if this is the only way that this will happen, you can trap that message, and then do the screenrect thing that Simon loves so much.

Craig

P.S. I could be wrong about there not being a message sent with the "maximize" button. Anyone Know?

[boqsc]

Ah,

Now I see what you mean by "not the way I want". It is how it is done, not, er, how it is done.

i don't think there is a message sent when the maximize button is pressed, but there is a message "resizeStack", that is sent when the stack is, er, resized.

So if this is the only way that this will happen, you can trap that message, and then do the screenrect thing that Simon loves so much.

Craig

P.S. I could be wrong about there not being a message sent with the "maximize" button. Anyone Know?

What you suggested is just a "blackhand" workaround, it not going to work correctly by the way.
From what i see, it can be serious problem for many developers. it may look like small thing in the developement sea, but trust me. It's not, if there is no way to do it - we need to make request and let the runrev livecode team hear about problem.
Going to wait for an answer, one more week...

[Simon]

Have you tried building your stack as a standalone?
Works like you want here.

Simon

[boqsc]

Have you tried building your stack as a standalone?
Works like you want here.

Simon

No it's not, maybe you can post the project test file that you use? (*.livecode *.REV)
And maybe the working exe file?

[Simon]

Hi boqsc,
Just take the stack you have there and build it as a standalone. You don't need any code in it.

Simon

[boqsc]

Hi boqsc,
Just take the stack you have there and build it as a standalone. You don't need any code in it.

Simon

Oh, well. Thats strange. It can be my problem before, that i set some properties that fixes the size of the stack. However it seems to work.
Realy big Thanx to everyone.

[jacque]

Just to save you some trouble, most of the time you can emulate how a standalone will work by just choosing "Suspend development tools" from the Development menu. That way you don't need to build standalones repeatedly while testing. A few things don't work (like a startup handler and in some cases, some of the open* messages) but for visual stuff it's pretty handy.