[Gambas-bugtracker] Bug #3031: Bug in WebListBox, WebDateBox, WebScrollView, WebProgressBar

[<bugtracker@xxxxxxxxxxxxxx>]

http://gambaswiki.org/bugtracker/edit?object=BUG.3031&from=L21haW4-

Comment #1 by Benoît MINISINI:

You should create several issues...

All bugs have been fixed in https://gitlab.com/gambas/gambas/-/commit/49d938790058f1e1e51d6b8198af311a717a2934, except the WebProgressBar which is not really a bug.

Here is the detail:

> WebListBox: 
> Click event: never fires.

Fixed.

> WebDateBox: 
> ReadOnly: When set to True programmatically or by the IDE, the object can always be edited.

Fixed.

> Click event: Never fired

Fixed.

WebScrollView:
	
> 1-At design time, if the ScrollView has an Arrangement property other than None and you then use the mouse to enlarge or reduce the size of the ScrollView, its content expands beyond the ScrollView's boundary, and the content can only be adjusted to the correct boundary with Arrangement = None.

Fixed. This was a bug in the IDE and in the ScrollView control (the desktop GUI one) that is used for representing the WebScrollView in the form editor.

> 2-If an object within the ScrollView has Focus and then the ScrollBar is scrolled, the object's Focus moves with the ScrollBar.

Fixed. But the focus rectangle is still visible even if the focused control is hidden because of the scrolling.

> 3-At runtime, if the ScrollView's content is cleared:
> ScrollView1.DeleteChildren()
> ScrollView1.Refresh()
> Then, when you try to add new objects:
> 3.1 If you don't set the Refresh() method, it generates an error: Invalid object.
> 3.2 If you set the Refresh() method, it does nothing.

Fixed.

> WebProgressBar: 
> You only see the end of the process, not the progress, in the bar.
> If you add a Wait 0.1, it will only freeze the program while the process completes, and at the end, you will see 100%.

Alas a 'gb.web.gui' application does not work like a desktop one, especially with the event loop. There is no GUI event loop, but a dialog between the server (your application) and the client (the browser).

The WAIT instruction is for the event loop of the server process, so it has no effect on the dialog between the browser and the application.

I will try to mimic the GUI event loop behaviour with a method like 'WebForm.Wait()', but I'm not sure it's possible all the time.

Benoît MINISINI changed the state of the bug to: Fixed.


----[ Gambas bugtracker-list is hosted by https://www.hostsharing.net ]----