Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.acorn.programmer > #6657 > unrolled thread

Hiding and revealing part of a window

Back to article view | Back to comp.sys.acorn.programmer

Contents

  Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-10 09:49 +0100
    Re: Hiding and revealing part of a window Martin <News04@avisoft.f9.co.uk> - 2026-07-10 10:06 +0100
      Re: Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-10 11:25 +0100
        Re: Hiding and revealing part of a window Steve Fryatt <news@stevefryatt.org.uk> - 2026-07-10 22:19 +0100
          Re: Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-11 10:32 +0100
            Re: Hiding and revealing part of a window Steve Fryatt <news@stevefryatt.org.uk> - 2026-07-11 16:33 +0100
              Re: Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-11 20:41 +0100
          Re: Hiding and revealing part of a window druck <news@druck.org.uk> - 2026-07-15 17:39 +0100
            Re: Hiding and revealing part of a window Steve Fryatt <news@stevefryatt.org.uk> - 2026-07-15 20:24 +0100
          Re: Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-16 11:05 +0100
            Re: Hiding and revealing part of a window Martin <News04@avisoft.f9.co.uk> - 2026-07-16 12:04 +0100
              Re: Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-16 12:48 +0100
                Re: Hiding and revealing part of a window Martin <News04@avisoft.f9.co.uk> - 2026-07-16 13:26 +0100
                Re: Hiding and revealing part of a window Harriet Bazley <harriet@bazleyfamily.co.uk> - 2026-07-16 14:26 +0100
                  Re: Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-16 14:50 +0100
                  Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-18 17:27 +0100
                    Re: Hiding and revealing part of a window Martin <News04@avisoft.f9.co.uk> - 2026-07-18 22:10 +0100
                      Re: Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-19 09:20 +0100
            Re: Hiding and revealing part of a window Jean-Michel <jmc.bruck@orange.fr> - 2026-07-16 17:45 +0200
              Re: Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-16 16:58 +0100
    Re: Hiding and revealing part of a window Kevin Wells <kev@kevsoft.co.uk> - 2026-07-10 16:37 +0100
      Re: Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-10 20:08 +0100
        Re: Hiding and revealing part of a window Harriet Bazley <harriet@bazleyfamily.co.uk> - 2026-07-12 12:12 +0100
          Re: Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-12 13:45 +0100
            Re: Hiding and revealing part of a window Harriet Bazley <harriet@bazleyfamily.co.uk> - 2026-07-12 23:19 +0100
        Re: Hiding and revealing part of a window Kevin Wells <kev@kevsoft.co.uk> - 2026-07-12 21:03 +0100
          Re: Hiding and revealing part of a window Steve Fryatt <news@stevefryatt.org.uk> - 2026-07-15 20:26 +0100
            Re: Hiding and revealing part of a window Kevin Wells <kev@kevsoft.co.uk> - 2026-07-17 21:06 +0100
    Re: Hiding and revealing part of a window J Peachey <john@jpeachey.co.uk> - 2026-07-10 21:15 +0000
      Re: Hiding and revealing part of a window Bob Latham <bob@sick-of-spam.invalid> - 2026-07-11 10:11 +0100

Page 1 of 2  [1] 2  Next page →

#6657 — Hiding and revealing part of a window

Words of guidance would be appreciated - thanks.

An application I'm writing has a secondary mode which for the most
part I want hidden. When the special mode is enabled, the main window
reveals the control panel for that mode.

Don't mind if the reveal is to the side or below the main window.

What is the easiest mechanism to achieve this?

Otherwise, I may have to create another window for these controls but
I'm not keen on that idea.


Thanks.

Bob.

[toc] | [next] | [standalone]

#6658

In article <5cf61ef6a3bob@sick-of-spam.invalid>,
   Bob Latham <bob@sick-of-spam.invalid> wrote:
> Words of guidance would be appreciated - thanks.

> An application I'm writing has a secondary mode which for the most
> part I want hidden. When the special mode is enabled, the main
> window reveals the control panel for that mode.

How is the 'special mode' enabled?
A button in the window, or some setting elsewhere?

> Don't mind if the reveal is to the side or below the main window.
> What is the easiest mechanism to achieve this?

Just set up the full window as you want, with reveal to right or
underneath, and just use the 'special setting' to determine the size
of the visible window when you use Wimp_OpenWindow

This perhaps assuming that there are no scroll bars enabled!

-- 
Martin Avison 
Note that unfortunately this email address will become invalid
without notice if (when) any spam is received. 

[toc] | [prev] | [next] | [standalone]

#6659

In article <5cf62095ccNews04@avisoft.f9.co.uk>,
   Martin <News04@avisoft.f9.co.uk> wrote:
> In article <5cf61ef6a3bob@sick-of-spam.invalid>,
>    Bob Latham <bob@sick-of-spam.invalid> wrote:
> > Words of guidance would be appreciated - thanks.

> > An application I'm writing has a secondary mode which for the most
> > part I want hidden. When the special mode is enabled, the main
> > window reveals the control panel for that mode.

> How is the 'special mode' enabled?
> A button in the window, or some setting elsewhere?

At the moment it is simply a setting in the app's config file just to
test the special mode algorithm but I will change that to either a
menu item or a button in the window. 

> > Don't mind if the reveal is to the side or below the main window.
> > What is the easiest mechanism to achieve this?

> Just set up the full window as you want, with reveal to right or
> underneath, and just use the 'special setting' to determine the size
> of the visible window when you use Wimp_OpenWindow

Yes, I can see that, I could manage it too.

> This perhaps assuming that there are no scroll bars enabled!

Unfortunately, they are enabled.

I don't know what the best thing to do is... stumped.

I may end up having a second window yet.


Thanks.

Bob.

[toc] | [prev] | [next] | [standalone]

#6663

On 10 Jul, Bob Latham wrote in message
    <5cf627bdb6bob@sick-of-spam.invalid>:

> I don't know what the best thing to do is... stumped.

Wimp_SetExtent is your frind in this case. Adjust the data block for
Wimp_OpenWindow (including the scroll offsets), call Wimp_OpenWindow, then
call Wimp_SetExtent. Make sure that you don't set the extent to less than
you have asked to be visible through Wimp_OpenWindow.

I know you're a BASIC and Assembler person, but I don't think that any of my
BASIC programs use variable sized windows. However, if you can read enough C
to be able to work out the parameters (it's all OSLib, so all of the Wimp
block entries are named sensibly), you can see how Puzzles adjusts its index
window extent here:

https://github.com/steve-fryatt/puzzles/blob/3308390778ca2fdd37ca4057311c8b97bc20a101/src/index_window.c#L826-L853

-- 
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/

[toc] | [prev] | [next] | [standalone]

#6665

In article <mpro.thz9x000u4xlm03ow.news@stevefryatt.org.uk>,
   Steve Fryatt <news@stevefryatt.org.uk> wrote:

> Wimp_SetExtent is your frind in this case. Adjust the data block
> for Wimp_OpenWindow (including the scroll offsets), call
> Wimp_OpenWindow, then call Wimp_SetExtent. Make sure that you don't
> set the extent to less than you have asked to be visible through
> Wimp_OpenWindow.

Oh that's interesting, I obviously need to read up about that.

> I know you're a BASIC and Assembler person, 

Almost all assembler but yes, I wish I wasn't if I'm honest, I feel
the constant need to apologise for it. Although I've purchased the
ROOL Dev suite I can't get into it. At work in the 90s I did a week
long C course and remember a lot of it and I was fine with a recent
Arduino project.

I think part of the problem is that unlike other languages and
systems, I've never seen a *very* simple wimp application created in
bits using the ROOL kit, so I have no starter examples.

> but I don't think that any of my BASIC programs use variable sized
> windows. However, if you can read enough C to be able to work out
> the parameters (it's all OSLib, so all of the Wimp block entries
> are named sensibly), you can see how Puzzles adjusts its index
> window extent here:

> https://github.com/steve-fryatt/puzzles/blob/3308390778ca2fdd37ca4057311c8b97bc20a101/src/index_window.c#L826-L853

I'll try. You gave similar advice last year about scrolling text in a
window. I couldn't understand the code but you did point me in the
right direction and I was then able to succeed. Trusty, very dated
PRMs. 

The text scrolling is great BTW. - Thanks so much.

Cheers,

Bob.

[toc] | [prev] | [next] | [standalone]

#6666

On 11 Jul, Bob Latham wrote in message
    <5cf6a6ba64bob@sick-of-spam.invalid>:

> In article <mpro.thz9x000u4xlm03ow.news@stevefryatt.org.uk>,
>    Steve Fryatt <news@stevefryatt.org.uk> wrote:
>
> > I know you're a BASIC and Assembler person,
> 
> Almost all assembler but yes, I wish I wasn't if I'm honest, I feel the
> constant need to apologise for it.

It was more an apology from my side that I didn't have a non-C example to
hand.

> I think part of the problem is that unlike other languages and systems,
> I've never seen a *very* simple wimp application created in bits using the
> ROOL kit, so I have no starter examples.

I'm not suggesting that you read it (although if it's useful, that's great),
but I should probably mention this guide. It starts with a very simple BASIC
example in Chapter 1, then converts it to C in Chapter 2 and goes on from
there. The target audience was people who knew C, had maybe written Wimp
applications in BASIC, but hadn't used C for the Wimp.

It's now got to 35 chapters (and still hasn't yet got to Wimp_SetExtent)...

  https://www.stevefryatt.org.uk/risc-os/wimp-prog

You'll need a "recent-ish" version of the DDE, though.

[snip]

> I'll try. You gave similar advice last year about scrolling text in a
> window. I couldn't understand the code but you did point me in the right
> direction and I was then able to succeed. Trusty, very dated PRMs.

I've just searched for Wimp_SetExtent in my project folders on the
off-chance, and it's pointed me to this:

  https://www.stevefryatt.org.uk/risc-os/panes/moving-the-furniture

which is a sort-of sibling to the tutorial above (there's other references
in the following chapter, too). It's about panes, but it does show
Wimp_SetExtent in use in BASIC -- the pane tutorial is all in BASIC for
accessibility.

Unfortunately, I couldn't find any applications of mine in BASIC which use
Wimp_SetExtent and that I'd consider a good example to suggest looking at
(it's all code that I wrote in the 1990s, before I had any idea what I was
doing -- if I even do now...).

:-)

-- 
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/

[toc] | [prev] | [next] | [standalone]

#6667

In article <mpro.ti0ojf0184uq504z4.news@stevefryatt.org.uk>,
   Steve Fryatt <news@stevefryatt.org.uk> wrote:
> On 11 Jul, Bob Latham wrote in message
>     <5cf6a6ba64bob@sick-of-spam.invalid>:

> > In article <mpro.thz9x000u4xlm03ow.news@stevefryatt.org.uk>,
> >    Steve Fryatt <news@stevefryatt.org.uk> wrote:


> I'm not suggesting that you read it (although if it's useful,
> that's great), but I should probably mention this guide. It starts
> with a very simple BASIC example in Chapter 1, then converts it to
> C in Chapter 2 and goes on from there. The target audience was
> people who knew C, had maybe written Wimp applications in BASIC,
> but hadn't used C for the Wimp.

> It's now got to 35 chapters (and still hasn't yet got to
> Wimp_SetExtent)...

>   https://www.stevefryatt.org.uk/risc-os/wimp-prog

> You'll need a "recent-ish" version of the DDE, though.

Yes, I really should stop making excuses, step out of my comfort zone
and get in there and that looks like a good start - thanks.

I will get further with my project first though, I've been on it 11
months now and with the new LanManFS coming I need to be ready.

Imagine, being able to easily connect to any NAS, be able to see the
full unicode and not have to fight Sunfish to do it !! :-)

> I've just searched for Wimp_SetExtent in my project folders on the
> off-chance, and it's pointed me to this:

>   https://www.stevefryatt.org.uk/risc-os/panes/moving-the-furniture

> which is a sort-of sibling to the tutorial above (there's other
> references in the following chapter, too). It's about panes, but it
> does show Wimp_SetExtent in use in BASIC -- the pane tutorial is
> all in BASIC for accessibility.

> Unfortunately, I couldn't find any applications of mine in BASIC
> which use Wimp_SetExtent and that I'd consider a good example to
> suggest looking at (it's all code that I wrote in the 1990s, before
> I had any idea what I was doing -- if I even do now...).

Ha, try being me for an hour, You would be sure then. :-)

Thanks.

Bob.

[toc] | [prev] | [next] | [standalone]

#6672

On 10/07/2026 22:19, Steve Fryatt wrote:
> On 10 Jul, Bob Latham wrote in message
>      <5cf627bdb6bob@sick-of-spam.invalid>:
> 
>> I don't know what the best thing to do is... stumped.
> 
> Wimp_SetExtent is your frind in this case. Adjust the data block for
> Wimp_OpenWindow (including the scroll offsets), call Wimp_OpenWindow, then
> call Wimp_SetExtent. Make sure that you don't set the extent to less than
> you have asked to be visible through Wimp_OpenWindow.

This is the solution I used for the DiscKnight choices window when the 
advanced options button is pressed. It's easier than messing around with 
two different windows. Works for Toolbox apps too.

---druck

[toc] | [prev] | [next] | [standalone]

#6673

On 15 Jul, druck wrote in message
    <1138d3k$1a5i3$1@druck.eternal-september.org>:

> It's easier than messing around with two different windows.

It is. Very much so. :-)

-- 
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/

[toc] | [prev] | [next] | [standalone]

#6675

In article <mpro.thz9x000u4xlm03ow.news@stevefryatt.org.uk>,
   Steve Fryatt <news@stevefryatt.org.uk> wrote:
> On 10 Jul, Bob Latham wrote in message
>     <5cf627bdb6bob@sick-of-spam.invalid>:

My extra panel is at the bottom of the window. So I assume this is
the minimum y settings.

So I create a window in WinEd that contains all elements including
the icons at the bottom which are usually hidden.

Okay done that.

> Adjust the data block for Wimp_OpenWindow (including the scroll
> offsets),

Adjust which parameters? What am I trying to achieve doing this? 

> call Wimp_OpenWindow, 

Okay.

> then call Wimp_SetExtent. 

To do what?
What am I trying to achieve doing this?


Sorry to be thick but I can't understand the principle of what you're
telling me to do. I need to understand before I can code something.


Thanks.

Bob.

[toc] | [prev] | [next] | [standalone]

#6676

In article <5cf93cf94dbob@sick-of-spam.invalid>,
   Bob Latham <bob@sick-of-spam.invalid> wrote:
> In article <mpro.thz9x000u4xlm03ow.news@stevefryatt.org.uk>,
>    Steve Fryatt <news@stevefryatt.org.uk> wrote:
> > On 10 Jul, Bob Latham wrote in message
> >     <5cf627bdb6bob@sick-of-spam.invalid>:

> My extra panel is at the bottom of the window. So I assume this is
> the minimum y settings.

> So I create a window in WinEd that contains all elements including
> the icons at the bottom which are usually hidden.

> Okay done that.

> > Adjust the data block for Wimp_OpenWindow (including the scroll
> > offsets),

> Adjust which parameters? What am I trying to achieve doing this? 

> > call Wimp_OpenWindow, 

> Okay.

> > then call Wimp_SetExtent. 

> To do what?
> What am I trying to achieve doing this?


> Sorry to be thick but I can't understand the principle of what
> you're telling me to do. I need to understand before I can code
> something.

I am confused as well! If you have a fixed main window area, but
sometimes you want to display another fixed area at the bottom of it,
then I would think you need to alter the Visible Area displayed, not
the Work Area (which Wimp_SetExtent does).

Create a window with two icons in WinEd, vertically spaced.
Then Menu => Work Area => Minimise & Update you will see the work
area X1 & Y1 shrink, and the scroll bars on the new window expand to
fill the bar.
But the DISPLAYED window does not change - you still see the two
icons.
If you now use Menu => Visible Area and reduce the Height by 50%,
when you click on Move the visible window will halve in height, and
you will probably only be able to see the top icon. 

Change the Visible height back to the original, and you will see both
icons again.

The change in Visible Area is done with a Wimp_GetWindowState, then
change just the visible min Y value and nothing else, then issue an
Wimp_OpenWindow.

However, if the main part of the window is of variable height, and/or
you need the scroll bars, then this simple way will not work, as the
extra bottom icons will need to move to the bottom of the window if
the top part changes size.

-- 
Martin Avison 
Note that unfortunately this email address will become invalid
without notice if (when) any spam is received. 

[toc] | [prev] | [next] | [standalone]

#6677

In article <5cf94257c7News04@avisoft.f9.co.uk>,
   Martin <News04@avisoft.f9.co.uk> wrote:
> In article <5cf93cf94dbob@sick-of-spam.invalid>,
>    Bob Latham <bob@sick-of-spam.invalid> wrote:
> > In article <mpro.thz9x000u4xlm03ow.news@stevefryatt.org.uk>,
> >    Steve Fryatt <news@stevefryatt.org.uk> wrote:
> > > On 10 Jul, Bob Latham wrote in message
> > >     <5cf627bdb6bob@sick-of-spam.invalid>:


> > Sorry to be thick but I can't understand the principle of what
> > you're telling me to do. I need to understand before I can code
> > something.

> I am confused as well! 

Thank heavens for that, if you don't grasp it .. 

> If you have a fixed main window area, but
> sometimes you want to display another fixed area at the bottom of
> it, then I would think you need to alter the Visible Area
> displayed, not the Work Area (which Wimp_SetExtent does).

That makes sense to me, I understand that.

Surely, if you reduce the Extent then you reduce the work area and
therefore remove from the window definition all the items in the area
you've chopped. 

[Snip]

> The change in Visible Area is done with a Wimp_GetWindowState, then
> change just the visible min Y value and nothing else, then issue an
> Wimp_OpenWindow.

Yes, I understand that too.

> However, if the main part of the window is of variable height,
> and/or you need the scroll bars, then this simple way will not
> work, as the extra bottom icons will need to move to the bottom of
> the window if the top part changes size.

Brain just exploded again. I can't understand that.

I think the problem is that the vertical scroll bar will be able, at
any time to reveal the hidden bottom section. I also think that
changing the extent is designed to fix that issue but I don't
understand exactly how.

Thanks.

Bob.

[toc] | [prev] | [next] | [standalone]

#6678

In article <5cf9465afdbob@sick-of-spam.invalid>,
   Bob Latham <bob@sick-of-spam.invalid> wrote:
> In article <5cf94257c7News04@avisoft.f9.co.uk>,
>    Martin <News04@avisoft.f9.co.uk> wrote:
> > In article <5cf93cf94dbob@sick-of-spam.invalid>,
> >    Bob Latham <bob@sick-of-spam.invalid> wrote:

> > If you have a fixed main window area, but sometimes you want to
> > display another fixed area at the bottom of it, then I would
> > think you need to alter the Visible Area displayed, not the Work
> > Area (which Wimp_SetExtent does).

> That makes sense to me, I understand that.

> Surely, if you reduce the Extent then you reduce the work area and
> therefore remove from the window definition all the items in the
> area you've chopped. 

Changing the Visible area does not affect the Work area.

Changing the Work area does not remove icons from the window
definition (though can affect the visible area, which must be in the
work area).

Changing either can result in icons becoming invisible, if they are
outside Visible or Work areas.

The only connection between Visible and Work areas are the Scroll
Offsets (which can make the brain hurt!) which determine which part
of the Work Area is Visible.

Enlarging Visible or Work areas can result in them becoming visible
again.

> [Snip]

> > The change in Visible Area is done with a Wimp_GetWindowState,
> > then change just the visible min Y value and nothing else, then
> > issue an Wimp_OpenWindow.

> Yes, I understand that too.

> > However, if the main part of the window is of variable height,
> > and/or you need the scroll bars, then this simple way will not
> > work, as the extra bottom icons will need to move to the bottom of
> > the window if the top part changes size.

> Brain just exploded again. I can't understand that.

> I think the problem is that the vertical scroll bar will be able, at
> any time to reveal the hidden bottom section. I also think that
> changing the extent is designed to fix that issue but I don't
> understand exactly how.

If the main part of the window is fixed size, and small enough to
display on the screen, why do you need scrollbars?

If you REALLY need scrollbars for the main part of the window, it
does become more complex.

-- 
Martin Avison 
Note that unfortunately this email address will become invalid
without notice if (when) any spam is received. 

[toc] | [prev] | [next] | [standalone]

#6679

On 16 Jul 2026 as I do recall,
          Bob Latham  wrote:

[snip]

> I think the problem is that the vertical scroll bar will be able, at
> any time to reveal the hidden bottom section. I also think that
> changing the extent is designed to fix that issue but I don't
> understand exactly how.
> 

In theory, if you change the maximum size of the window work area then
the scrollbars can no longer scroll beyond that.  (And since it's
possible for icons to be located outside the edge of the window - no
sanity checks! - changing it back should reveal the icons down at the
bottom again, in the position in which they were originally created.)

I haven't tested this....

-- 
Harriet Bazley                     ==  Loyaulte me lie ==

A chicken is an egg's way of producing more eggs.

[toc] | [prev] | [next] | [standalone]

#6680

In article <815a4ff95c.harriet@bazleyfamily.co.uk>,
   Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:
> On 16 Jul 2026 as I do recall,
>           Bob Latham  wrote:

> In theory, if you change the maximum size of the window work area
> then the scrollbars can no longer scroll beyond that.  (And since
> it's possible for icons to be located outside the edge of the
> window - no sanity checks! - changing it back should reveal the
> icons down at the bottom again, in the position in which they were
> originally created.)

Yes, I hope so, working at it right now...


> I haven't tested this....

Nor me - YET.

Thanks.

Bob.

[toc] | [prev] | [next] | [standalone]

#6685

In article <815a4ff95c.harriet@bazleyfamily.co.uk>,
   Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:
> On 16 Jul 2026 as I do recall,
>           Bob Latham  wrote:

> [snip]

> > I think the problem is that the vertical scroll bar will be able,
> > at any time to reveal the hidden bottom section. I also think
> > that changing the extent is designed to fix that issue but I
> > don't understand exactly how.
> > 

> In theory, if you change the maximum size of the window work area
> then the scrollbars can no longer scroll beyond that.  (And since
> it's possible for icons to be located outside the edge of the
> window - no sanity checks! - changing it back should reveal the
> icons down at the bottom again, in the position in which they were
> originally created.)

> I haven't tested this....

I've got it working !!!

I've modified my Wimp_OpenWindow code to reduce the window height by
increasing the value of the minimum Y visible area. That raised the
bottom of the window as expected but the scroll bars can pull it back.

Next I used Wimp_SetExtent to remove that bottom area. That removes
the scroll bar recovery option.

In both cases I used the same variable which if set to 130 chops that
off the bottom but if set to zero it leaves the window full size.

Of course to make the window full size again the process needs to be
reversed so set the extent first and then re-open the window.

All exactly as Steve suggested and it worked.

I had always thought items outside the work area would be lost but
actually, not so.

Thanks to everyone who helped.

Not at all sure what to do about the scroll bar...


Cheers,

Bob.

[toc] | [prev] | [next] | [standalone]

#6686

In article <5cfa679cf3bob@sick-of-spam.invalid>,
   Bob Latham <bob@sick-of-spam.invalid> wrote:
> Not at all sure what to do about the scroll bar...

Why do you need the scroll bar?
Is the main window height larger than can be displayed on the screen
easily? 

If not, just remove the scroll bar.
Then you would not need to mess about with SetExtent.

-- 
Martin Avison 
Note that unfortunately this email address will become invalid
without notice if (when) any spam is received. 

[toc] | [prev] | [next] | [standalone]

#6688

In article <5cfa817ebeNews04@avisoft.f9.co.uk>,
   Martin <News04@avisoft.f9.co.uk> wrote:
> In article <5cfa679cf3bob@sick-of-spam.invalid>,

> Why do you need the scroll bar?
> Is the main window height larger than can be displayed on the screen
> easily? 

> If not, just remove the scroll bar.
> Then you would not need to mess about with SetExtent.

A valid point for sure.

It's not a glaring issue so I'll leave it for now, come back to it
later and have a think.

Cheers,

Bob.

[toc] | [prev] | [next] | [standalone]

#6681

In message <5cf93cf94dbob@sick-of-spam.invalid>
          Bob Latham <bob@sick-of-spam.invalid> wrote:

> In article <mpro.thz9x000u4xlm03ow.news@stevefryatt.org.uk>,
>    Steve Fryatt <news@stevefryatt.org.uk> wrote:
>> On 10 Jul, Bob Latham wrote in message
>>     <5cf627bdb6bob@sick-of-spam.invalid>:

> My extra panel is at the bottom of the window. So I assume this is
> the minimum y settings.

> So I create a window in WinEd that contains all elements including
> the icons at the bottom which are usually hidden.

> Okay done that.
Is it a window with an internal toolbar?


>> Adjust the data block for Wimp_OpenWindow (including the scroll
>> offsets),

> Adjust which parameters? What am I trying to achieve doing this?

>> call Wimp_OpenWindow,

> Okay.

>> then call Wimp_SetExtent.

> To do what?
> What am I trying to achieve doing this?


> Sorry to be thick but I can't understand the principle of what you're
> telling me to do. I need to understand before I can code something.


> Thanks.

> Bob.



-- 
Jean-Michel

[toc] | [prev] | [next] | [standalone]

#6682

In article <221c5cf95c.jmb@jmc.bruck.orange.fr>,
   Jean-Michel <jmc.bruck@orange.fr> wrote:

> Is it a window with an internal toolbar?

Not really. It's just a window with icons. Some of those icons at the
bottom of the screen I would like to hide unless they're needed.

Thanks.

Bob.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.sys.acorn.programmer

csiph-web