beginners question about Hug

[axelmoe]

Hi all,
i am new in BECON. At first thank you for this fantastic programming and Development environment.

hier my first questions:

I wich to limit the input length in HUG entry. Whats the best way?
I want to allow only numeric entries in a Hug entry. Whats the best way?

many thanks for your support.

Regards from Germany

Axel

[vovchik]

Dear Axel,

Have a look at this:

GTK

After creating the widget, you can set the property, eg:

SETPROPERTY(entry_widget, "width-chars", 10)
SETPROPERTY(entry_widget,"text-length", 10)

And you can use GRAB$ in a CALLBACK function for the widget to check the input until you get what you need from the user.

With kind regards,
vovchik

[alexfish]

Hi Axel


have expanded Vovchik's SETPROPERTY


A couple of option are in the subs



INCLUDE hug.bac

SUB set_numb()

nm# = VAL(GRAB$(entry_widget2))
new_numb$= STR$(nm#)

     TEXT(entry_widget2, new_numb$)

END SUB

SUB new_numb()

nm# = VAL(GRAB$(entry_widget))

IF nm# > 0 THEN

new_numb$= STR$(nm#)
TEXT(entry_widget, new_numb$)

ELSE

TEXT(entry_widget,"Number Req")

END IF

END SUB



LET win = WINDOW("entry", 300, 200)

LET entry_widget = ENTRY("", 100,25)
ATTACH(win,entry_widget,10,10)

SETPROPERTY(entry_widget, "width-chars", 10)

CALLBACK(entry_widget,new_numb)

LET entry_widget2 = ENTRY("", 100,25)
ATTACH(win,entry_widget2,10,40)

SETPROPERTY(entry_widget2, "width-chars", 10)
REM set the entry to the right
SETPROPERTY(entry_widget2, "xalign", 1.0)

CALLBACK(entry_widget2,set_numb)

DISPLAY


BR
Alex

[axelmoe]

Hi all,

many thanks for your extensive answers.


rgds

Axel

[axelmoe]

Hi all,

this settings
++
SETPROPERTY(entry_widget, "width-chars", 10)
SETPROPERTY(entry_widget,"text-length", 10)
++

have shown no effect in my tests.

The check for numerc entrys work but I want to permit directly at the keystroke only digits.

Can someone help me?


Thanks + regrads

Axel

[vovchik]

Dear Axel,

Here is a tiny python script that does that. Easy to port to BaCon, but I am in a rush right now:


#!/usr/bin/env python
import gtk
import pygtk

class xEntry(gtk.Entry):
   def __init__(self, allowedchars):
       gtk.Entry.__init__(self)
       self.allowedchars=allowedchars
       self.connect("changed", self.charcheck, None)

   def charcheck(self, widget, string, *args):
       pos = widget.get_position()
       char = widget.get_chars(pos, pos + 1)
       if char not in self.allowedchars:
           widget.select_region(pos, pos + 1)
           widget.delete_selection()


class MainWindow(gtk.Window):
   def __init__(self):
       print "111"
       gtk.Window.__init__(self,gtk.WINDOW_TOPLEVEL)
       self.entry = xEntry("1234567890.")        
       self.box = gtk.VBox()
       self.box.pack_start(self.entry)
       self.add(self.box)
       self.show_all()

def main():
   m=MainWindow()
   gtk.main()

if __name__ == "__main__":
   main()


With kind regards,
vovchik

[axelmoe]

hi all,

the parameter for SETPROPERTY is

max_length

axel

[axelmoe]

Hi all,

I have found teh HUG function KEY but I don't understand the usage.
Can someone provide me an example.

Thanks

Axel

[Pjot]

Hi Axelmoe,

Please check out my Landscape program which I posted earlier.

HTH
Peter

[alexfish]

Hi Axel

Can look at the key options , here not sure if it will work 100% , this can relate to the IM input options, hence if the key press event distracts the focus away from the
widget then possible focus for input may = null ..

developer.gnome.org/gtk2/stable/ look at both the gtk2 entry + the entrybuffer .. this points to a no valid read of key event unless specific to the function
IE the Entry requires the Enter Key event.. (but can allow an over-ride as explained in the IM on the entry buffer..

one possible option if met with failure . use multiple entry's to the number of digits required , then after each input focus on the next box , or what ever

BR Alex

EG::


INCLUDE hug.bac

SUB check_input(NUMBER widget)
PRINT "changed"

SELECT widget
CASE entry_widget
PRINT "box1"
FOCUS(entry_widget2)

CASE entry_widget2
PRINT "box2"

END SELECT

ENDSUB

LET win = WINDOW("entry", 300, 200)

LET entry_widget = ENTRY("", 15,25)
SETPROPERTY(entry_widget,"max-length",1)
ATTACH(win,entry_widget,15,40)
CALLBACK(entry_widget,check_input)
LET entry_widget2 = ENTRY("", 15,25)
SETPROPERTY(entry_widget2,"max-length",1)
ATTACH(win,entry_widget2,30,40)
CALLBACK(entry_widget2,check_input)
REM focus on first entry box
FOCUS(entry_widget)
DISPLAY


[alexfish]

Hi Axel

Here have taken the hug key event routine + add some mods to it.

There is still work to be done as regards adding code , hence added print + select to help U on the way


BR
Alex


INCLUDE hug.bac


FUNCTION  get_entry_key(NUMBER hug_widget, void *hug_data1, NUMBER hug_data2) : REM INCLUDE

LOCAL inkey
USEC
typedef struct {
int type;
void *entry;
signed char send_event;
unsigned int time;
unsigned int state;
unsigned int keyval;
} GdkEventKey;

GdkEventKey *keypress;
keypress = (GdkEventKey*)hug_data1;

inkey = keypress->keyval;

END USEC
REM can sort the bits here
PRINT inkey , " : " , inkey FORMAT "%d %s %c \n"

SELECT inkey

CASE 48

PRINT "0"

CASE 49

PRINT "1"

CASE 50

PRINT "2"

CASE 51

PRINT "3"

CASE 52

PRINT "4"

CASE 53

PRINT "5"

CASE 54

PRINT "6"

CASE 55

PRINT "7"

CASE 56

PRINT "8"

CASE 57

PRINT "9"
DEFAULT

REM do something here as well

PRINT "Err"

END SELECT

RETURN FALSE

END FUNCTION

LET win = WINDOW("test entry key event",600,400)

LET entry_widget = ENTRY("",200,25)

SETPROPERTY(entry_widget,"max-length",10)

g_signal_connect_data(entry_widget, "key-press-event", get_entry_key, 0, 0, 0)

ATTACH(win,entry_widget,20,20)

FOCUS(entry_widget)

DISPLAY


[axelmoe]

Hi All,

many thanks for your grreat examples. My first test's lokked fine.
I'll create an example wich is demonstrating the me now variants of input check.

rgds

Axel

[vovchik]

Dear Alex and Alex,

What about this?


INCLUDE hug.bac

' ------------------
FUNCTION NUMERIC_FILTER(NUMBER hug_widget)
' ------------------
' here, '-' for negative and '.' for decimal nums are OK
' but there must be a better way to write the REGEX
' - i.e [[:digit:]], plus '-' and '.'
IF REGEX(GRAB$(hug_widget), "[[:alpha:] ~`!@#$%^&*()_+=<>?]") THEN
TEXT(hug_widget, "")
END IF
RETURN FALSE
END FUNCTION

' ------------------
FUNCTION PRINT_ENTRY(NUMBER hug_widget)
' ------------------
PRINT GRAB$(entry_widget)
RETURN FALSE
END FUNCTION

' ------------------
SUB MK_GUI()
' ------------------
win = WINDOW("Filter entry input", 300, 100)
entry_widget = ENTRY("", 200, 25)
but = BUTTON("OK", 90, 30)
ATTACH(win, entry_widget, 20, 20)
ATTACH(win, but, 200, 60)
SETPROPERTY(entry_widget, "max-length", 10)
g_signal_connect_data(entry_widget, "changed", NUMERIC_FILTER, 0, 0, 0)
FOCUS(entry_widget)
CALLBACK(but, PRINT_ENTRY)
END SUB

MK_GUI()
DISPLAY


With kind regards,
vovchik

[axelmoe]

Hi vovchik,

great, very great. that is what I am searching for. I will test it in a short time.
From my point of view an another great way of implementing this things do some thing like this:

mail.gnome.org/archives/gtk-list/2001-December/msg00151.html

Thanks + rgds

Axel

[vovchik]

Dear Axel,

I think this is a neater, better way to write the numeric filter (but still needs improvement):


' ------------------
FUNCTION NUMERIC_FILTER(NUMBER hug_widget)
' ------------------
IF ISFALSE(REGEX(GRAB$(hug_widget), "[[:digit:].-]")) THEN
TEXT(hug_widget, "")
END IF
RETURN FALSE
END FUNCTION


but I like the idea of masks and templates described in the link you provided. We'll have to think of how to implement something like that, which would be very useful.

With kind regards,
vovchik