forums.silverfrost.com

[rudnei]

Hi,

I am experiencing a problem with my application; I am using a single window (%ww) with three different %gr areas in the window,

rslt=winio@('%ww%ca[FLUXOVIZ]&')
rslt=winio@('%1.2ob[raised]&')
rslt=winio@('%cn%ws%nl&','Painel de Controle')
rslt=winio@('%`^gr[black,rgb_colours]&',painel%xmax-painel%xmin+1,painel%ymax-painel%ymin+1,&
id_painel_de_situacao,painel_de_situacao)
rslt=winio@('%cb&')
rslt=winio@('%`gr[white,rgb_colours]&', &
barra_cores%xmax-barra_cores%xmin+1,barra_cores%ymax-barra_cores%ymin+1,&
id_barra_cores)
rslt=winio@('%cb&')
rslt=winio@('%ob[no_border]&')
rslt=winio@('%`^gr[black,rgb_colours,full_mouse_input,box_selection]&', &
tela%xmax-tela%xmin+1,tela%ymax-tela%ymin+1,&
id_tela,trata_mouse)
rslt=winio@('%cb&')
rslt=winio@('%lw',janela_principal)

and would like to resize the one highlighted above, but if a use a %pv and the option user_resize, when I resize the window, the other two graphics areas move out of place...

I prefer to use three graphics areas since I can keep coordinates which are unique to each and can just select the desired graphics region...

Cheers
Rudnei

[PaulLaidler]

rudnei

I suggest that you post a simple and complete program that illustrates what you want to do. Then others can try out different strategies.

The best answer might be to do the resizing via the new design mode (which I plan to demonstrate on Youtube shortly). This provides an alternative resizing method that might do what you want.

p.s. "shortly" = about two weeks.

[LitusSaxonicum]

If you have 3 %gr areas, then you have separate coordinate systems for each, and a different callback for each, but it is much easier to keep it all in one %gr, and simply work out which one you are ina at any time. For example, if you have 3 pseudo %gr field all top aligned, your callback only has to test for the x coordinate (and so on).

Doing things in one %gr also makes the division bars movable independently, for example with 2 areas top aligned and one below them taking the full width, then you can test the pixel position and if you are in the horizontal bar you can change the cursor to arrange resizing vertically, or do the same with the vertical bar.If nice cursors aren't already in Windows/Clearwin+, there are plenty downloadable on the web. I sometimes use the 'smooth' cursors by Vlastimil Miler - they're excellent.

Eddie

[rudnei]

Hi,

Following Paul's request, here is an example based on the same structure my actual program is as of now:

[rudnei]

And here is part 2 of the code:

[rudnei]

and part 3...

[rudnei]

and part 4...

[rudnei]

Dear John,

Thanks for your reply. Indeed this sample have some side-effects from trimming the actual code, as you have pointed out; item 1 specifically I have no idea at all since the only control I have is via the event GRAPHICS_RESIZING...

But the main thing is: how do I create this MDI? I don't have Visual Studio available... can I do it directly with ClearWin+ ?

Cheers
Rudnei

[rudnei]

Dear John,
I have been looking into the last code provided in the topic you mentioned.

Looks like it will do the trick; I'll try with my application and get back to you.

Cheers!
Rudnei

[rudnei]

Hi John,

I have modified the code supplied in the aforementioned topic; however, the window captioned "Simulation" is not resizable... any ideas on how to do it?

Cheers
Rudnei

winapp
program test_mdi1
implicit none
include <windows.ins>
integer :: i1,i2,i3,i4,rslt,main_window,&
control_panel=1,display_bar=2,simulation=3

i1=winio@('%ca[Main Window containing an MDI frame]&')
i1=winio@('%ww[no_frame,not_fixed_size]&')

i1=winio@('%pv%fr&',1800,1000)
i1=winio@('%lw',main_window)

i2=winio@('%ww[no_frame]%ca[Control Panel]%`gr[black,rgb_colours,metafile_resize,smooth8]&', &
200,200,control_panel)
i2=winio@('%aw',main_window)

i3=winio@('%ww[no_frame]%ca[Display Bar]%`gr[white,rgb_colours,metafile_resize,smooth8]&', &
100,400,display_bar)
i3=winio@('%aw',main_window)

i4=winio@('%ww[no_frame,not_fixed_size]%ca[Simulation]%`gr[black,rgb_colours,metafile_resize,smooth8]&', &
800,800,simulation)
i4=winio@('%aw',main_window)

! Desenha no painel de controle
rslt=select_graphics_object@(control_panel)
call draw_filled_ellipse@(100,100,80,80,rgb@(127,59,30))

! Desenha na barra de cores
rslt=select_graphics_object@(display_bar)
call draw_filled_rectangle@(2,2,398,398,rgb@(255,255,30))

! Desenha na �rea de simula��o
rslt=select_graphics_object@(simulation)
call draw_filled_rectangle@(10,10,200,200,rgb@(30,255,30))
call draw_filled_rectangle@(100,50,120,60,rgb@(255,0,30))
call draw_filled_rectangle@(400,400,600,5000,rgb@(30,0,255))

end program test_mdi1

[DanRRight]

I hear in my Antarctica how you guys are swearing trying to tame this wild horse called Clearwin. Even i did when tried to fix, did you hear my french? Company must make 100000 demo examples, not 10-15 like all these 20 years. Here are all 4 windows resizable (added text window), "rgb_colours" are now redundant, %es (Escape key) makes debug easier. Used iTextUnit=2 may work only for version 8.30, before it was =0

[rudnei]

Thanks for your help!

[DanRRight]

Noticed that while I made windows resizable the first two windows' surprisingly lost the ability to plot (display_bar and control_panel)? This may take some more swearing to find why.

[DanRRight]

Hell knows, way to many options to try. Needs more swearing time. This is why i use word 'devilry' too often.

[DanRRight]

I took your contribution and now it plots on each screen but still does not work right.

Why handle for each of 3 graphics windows are all the same is a good question. Due to that every time we click on any window the plotting goes to the last screen instead the current one

Here is what i changes in your code:

1) each callback calls select_graphics_object@ function before doing any drawings. And

2) the callback does have value 2 not zero at the end, this is default for Clearwin+ . Zero might be used if you want to close window on any click on it

3) i removed "implicit none" as it made me nuts and swear louder very quickly asking to declare each and every damn junk variable i introduce like i44 in each and every subroutine. Or requiring to declare each variable in common blocks in all these Functions. To avoid that requires using modules but modules have another bad property: when your code will grow one big module will eventually swallow all others making one huge monopoly which has nothing more but die

We may continue to swear...err...try some more permutations before asking Paul to comment, i have couple other demos which actually worked pretty well switching graphics windows.