World: r3wp

windows 7 - same problem with tour.

Works on XP. Did previous versions of RebGUI/tour.r exhibit this 
problem on Windows 7?

never tried on w7 before

build 118 looks okay on W7

Dunno if you changed the "Menu" around but sample is square in the 
middle but at the top in B200

Bug (the #V directive is failing).

Ah, page color under Windows is wrong. It should be:

	colors: make object! [
		page: either OS = 'Mac [232.232.232] [white]

Graham, you mentioned in the Linux group that you had to change the 
RebGUI front from Verdana to something else. What font did you end 
up using?

Hmm, Rebgui somehow changed from single color web like look to some 
W9x look, was there any reason?

Ashley, that was a long time ago .. where would I have changed the 
font? :)

request-char somehow misbehaves here.  1) the scroller is of wrong 
size, when window appears 2) right area is drawn without the box, 
which starts to appear, when I mouse over edge chars 3) consecutive 
display of request-char displays much larger screen (run from RebDOC 
interface)

request-char crashed for me.

I clicked on request-char in rebdoc.r and got this


** Script Error: request-progress expected steps argument of type: 
integer
** Where: get-fonts
** Near: request-progress/title (length? s) / 3 [
    foreach [fn reg style] s [
        fn: trim first parse/all fn "("
       ...
>>

so fonts must be handled differently in w7s

where do I set my UI options? I can't somehow remember, how should 
I populate it :-)

used to be a requestor

get-fonts crashes with same error

hmm, SVN says:

RebGUI v2 RC1

Added
	icon
	get-fonts
	confirm
	request
	request-calc
	requesst-verify
	rebface/old-color
	rebface/over?

Reimplemented
	arrow
	calendar
	drop-list
	password
	slider
	tool-bar
	set-state
	set-color

Enhanced
	chat
	edit-list
	spinner
	table
	request-char
	request-font

Removed
	question
	request-ui
	pie-chart
	symbol
	options [info no-click]
	options [arrow options]

WIP
	A disable/enable function and layout option
	Rewrite of led widget
	Rewrite of tree widget

So no more ability to change UI settings ....

Did anyone use that?

I used it, to set boxy design instead of rounded, and also to change 
some colors. I for one like scroller/dragger look, but don't like 
gradiented buttons/tabs ... they look like W9x, which is imo a bit 
of UI regression. I thought Ashley wanted to go more web way, not 
desktop app way (from the design pov)  ...

But overall it looks good.

is it using a smaller font?

everything seems much smaller

I would welcome tour.r would fit 1280x800 notebook :-) I can't see 
buttons nor the top bar, a bit tricky to handle :-)

used to fit .

Windows XP with 1366 x 768


After start of tour.r the upper border is outside the screen and 
the status line not visible.

After moving the window down with the cursor keys, the status line 
gets visible.

After moving  the cursor to the upper edge with every click there 
the main windows moves down a step.

changed from single color web like look to some W9x look, was there 
any reason?
 ... commercial reality ;)
where would I have changed the font?
 ... ctx-rebgui/effects/font
request-char somehow misbehaves here
 ... bug, noted
fonts must be handled differently in w7s

 ... I don't have access to W7 at home, but will check this Monday 
 at work
where do I set my UI options?

 Design time with ctx-rebgui/effects, /colors /behaviors and /sizes

 Adding request-ui back so you can alter these values from a GUI is 
 trivial ... what I've removed is the rebind logic that enabled you 
 to dynamically change values (i.e. you would have to re-do %rebgui.r 
 to see any UI changes take effect ... not very practical for an SDK 
 app)
they look like W9x

 ... the color scheme (with the colors/page change noted above) is 
 taken straight from W7
don't like gradiented buttons/tab
 ... based on W7 and Mac
I thought Ashley wanted to go more web way, not desktop app way

 ... I've actually gone for something halfway (simpler than OS, more 
 complex than Web)
is it using a smaller font?

 ... 12pt by default as always (maybe W7 renders it differently than 
 XP?)
everything seems much smaller
 ... bigger screen? ;)
I would welcome tour.r would fit 1280x800 notebook

 ... RC1 is about getting the basic functionality right, %tour.r and 
 %RebDOC.r will both be made to run 1024x768
used to fit
 ... they havn't been reworked yet
Windows XP with 1366 x 768 ...
 ... will be fixed with above

Build 201 uploaded
- Added request-error
- Enhanced request-verify
- Added set-enable
- Added set-disable
- Added layout disable option
- Enhanced led widget
- Enhanced radio-group

Example disable/enable usage

display "test" [
	f: area "Blah" disable
	button "Enable" [set-enable f]
	button "Disable" [set-disable f]
]
do-events

sorry. I was not detailed enough,

the status line is not visible in the first place, although the lower 
border is inside the screen.

It's not possible to move the window with cursor keys, as it always 
snaps back.

It's not possble to resize the window by catching the upper edge 
with the mouse, as it always snaps down.
I hope I am clearer now.

where can I download this again? sorry for not keeping up. :-)

Could drop-downs be closed by clicking outside of them? Only ESC 
is possible right now ...

Henrik .. just do a google search for rebgui codeplex

I found this in my code:


#if [linux][
    set-fonts/name "helvetica"
    set-fonts/size 12
]

thanks, got it

Build 202 uploaded ( https://rebgui.svn.codeplex.com/svn/)
- Fixed password
- Added icon to tour.r
- Resized tour.r to fit smaller screens

- Reworked layout and display functions to remove duplicate show 
and do-events calls
- Removed do-events from tour.r and RebDOC.r


The layout/display change (apart from correcting numerous rendering 
anomolies and improving layout speed) may have caused other unforseen 
side-effects. At the very least it changes RebGUI in the following 
manner; previously you would write:

	display "A" [...]
	print "A"
	do-events

and get "A"  printed to the console. Now you write:

	display "A" [...]
	print "A"


and only get "A" printed to the console once the display has been 
closed. This now lets you write code like:

	display "A" [ ;do some stuff to set result]
	process result and display "B" or "C" based on result

This change is still experimental so let me know what you think.


Also, who actually uses tool-tips??? I've been debating whether to 
fix them so they work properly, or just remove them entirely. Thoughts?

I'd like to use them one day .. but never have got around to doing 
so.

never used tooltips, but sometimes with another apps I welcome them, 
to find description for icons ....

One note to drop-list. Apart from the fact, that it can be closed 
only by pressing ESC, it does a little bit weird thing - it remembers 
its last mouse-over element. So mouse-over some drop-list item, then 
go-away from it, then press ESC. The value of drop-list changes to 
that last remembered mouse-over one ...

Yep, I need to rework the popup logic (drop-lists, edit-lists, menus) 
a bit. There was/is a lot of code to work around non-existant view 
bugs (which were present pre View 1.3). Most of the weird exceptions 
are now caused by the little-used tool-tip code! ;)

Just wondering if when there are major changes, if they can be uploaded 
to a different branch for testing before being committed to the main 
trunk.

Sounds like display is now always modal??

That's a major change .. like changing from view/new to view

Doesn't this break lots of things?

I am just trying new RebGUI and like it a lot. There is one, at least, 
big problem with disable.

Sorry for breaking my message. Hopeffuly changed settings will work 
now.

>> display "" [panel data [button] disable panel data [button] disable] 
  ;;== it only disables second panel and first can't be disabled 
even later in code

Sounds like display is now always modal?

 ... I thought modal is when only the active dialog/popup can accept 
 user input? That's still the case, try the follwing:

	display "Test" [
		area
		button "A" [display "A" [button]]
		button "B" [alert "B"]
	]


Press "A" and type some text into the area, then close "A" and try 
the same thing with "B".

Marek, good pickup ... I'll add that to the list of fixes.

Another discovery. One can only select one table at a time. This 
is more serious problem, me thinks. The previous one seems to work 
later, but directtly from display.
And it seems tha I can send more than 1 line at the time now.