Need XP / Vista testing please :-)

Hallo,

Am currently working on a Console GUI module, and would be grateful if someone could test this small app on XP or Vista please, as I'm on Win2K here. (file is HERE)

This test is to show the UI running via Events.

When you run it, you should see a clock in the top-right, and a text entry field in the middle. To finish the edit you can use Escape, Enter or Tab.

This is the source :

SuperStrict

Framework BaH.Curses
Import BRL.Timer
Import BRL.EventQueue

Local timer:TTimer

Global timeLabel:TCursesLabel = TCursesLabel.Create(POS_RIGHT, POS_TOP, [CurrentTime()])

Local entry:TCursesEntry = TCursesEntry.Create(POS_CENTER, POS_CENTER, "<C>Enter some text.", ..
		"</U/5>Text:<!U!5>", A_NORMAL, ".", vMixed, 40, 0, 256)

If timeLabel Then

	timeLabel.show()

	timer = CreateTimer(1)
	AddHook EmitEventHook, eventHook, timer

	' entry will accept key input
	SetFocus(entry)
	
	While True
		WaitEvent()
		Select currentEvent.id
			Case EVENT_GADGETACTION
				Select currentEvent.data
					Case vNORMAL
						popupLabel(["<C>You typed", "", "<C>'" + entry.getValue() + "'"])
					Case vESCAPE_HIT
						popupLabel(["<C> You aborted the entry by hitting escape!! "])
				End Select
				Exit	
		End Select
	Wend

End If

Function eventHook:Object(id%, data:Object, context:Object)

	If TEvent(data) Then
		If TEvent(data).id = EVENT_TIMERTICK
			timeLabel.setText([CurrentTime()])
			timeLabel.getScreen().refresh()
		End If
	End If

	Return data
End Function

Just let me know if it runs okay and if it flickers a lot or not.

Thanks muchly :-)

I just tried it in XP (Pro SP2). It runs without flicker and works as you describe. Pressing Escape results in a "pop up" stating that fact, while pressing Tab or Return results in a pop up showing what was typed.

In the interest of (probably excessive <g>) testing, I tried dragging the window. During that, the clock updates every second though text input isn't possible (as usual for a BlitzMax non-GUI app).

I also took the liberty of trying it in Win 98 SE, and it worked fine there, too.

Works fine on my laptop with XP SP1 installed. The timer flickers occasionally, but it is very minor.

Does work here on my XP as well.
Tab, Enter, ESC, del, Backspace, key-repeat as expected
The clock flickers sometimes during update a tiny bit, but not related to fast input. Not that problem, all in all quite good.

works for me too.

What you posted from your worklog seems really interesting - I'm looking forward to this module! ;-)

I can confirm this works, as WendellM described, on Vista 32-bit too! I didn't notice any flickering at all...

Thanks folks. Much appreciated :-)

The "flicker" is due to the fact that the curses code wants to redraw everything when you tell a widget to refresh itself. Tried my best to minimize that. Shows up most on Windows and Mac, while on Linux you can't see it at all.


Probably because the Key input event handling isn't done through an EventHook... Maybe. Or it just won't work like that.
I had to jump through a lot of hoops just to get this event-model to work (that and trawling through many, many google searches)

Making good progress, I think. This event stuff opens up lots of potential for quite complex BlitzMax console apps :-)

I only even tried it since your clock was updating so nicely while being moved. There probably aren't any real-world situations where the user would actually need to type in text while moving the window.

Brucey,
while playing a bit more and testing CTRL things i found that using CTRL and one of the 0-9 and ;',./-=+? and may more just quits the program.
While CTRL f (forward) CRTL b (backward) CTRL a (home) CTRL e (end) works ok for me.
CTRL n for next is like enter which is probably ok, while p does nothing?

EDIT: btw. copy and paste, should they work?

Surprisingly, it appears to - if you use the "standard" windows copy/paste method of highlighting with the mouse then right clicking to copy, and then right-clicking again to paste.

Haven't tested the CTRL handling too much as yet - except for CTRL-C. I'm sure there's a way to catch/ignore them (one would hope so, anyways!).

The problem I've had while testing is that Debugging don't work. I do believe it is due to the way BlitzMax uses stdin/out to pass around debug info. And you can't run a debug app from the IDE - because it needs to run from a "shell" type window. Slows down the work a bit, but it does mean I have to be right first time, more often than usual ;-)

Curses is a big fish, and I've only really touched on the surface so far.