In Form Data mode Tab is used to move to the next field, and Ctl+Tab to move to the preceding field. Whereas Tab does take you to the next field, Ctl+Tab does not take you to the preceding field. Reproducible: Always Steps to Reproduce: 1. Open a Form in Data Mode 2. Mouse-click to position you in a central field 3. Use Tab to move forward to the next field 4. Use Ctl+Tab to move backwards to the preceding field Actual Results: Ctl+Tab does not move the focus to the preceding field Ctl+Tab moves the cursor to the end of the text in the field Expected Results: Ctl+Tab should move focus to the preceding field There is some odd behaviour, maybe depending on what type of field, (whether a Text Box or a Text Editor type?), associated with tabbing around the fields. For instance, in one area I can Ctl+Tab back but the initial field is still shown with the 'focus line' around while the data in the preceding field is highlighted.
Thanks Ian. Default shortcut for for the "backtab" action is Shift+Tab, not Ctrl+Tab. Do you mean Shift+Tab? Using Shift+Tab I am able to repeat your tasks 1-4 properly but the form you're testing may behave different. I'd appreciate if I can test the form (no data needed, just the form). It can be sent to me privately or attached below. If you're using server db, I can give instructions how you can extract the form information for me.
Jaroslaw, yes in error there, Shift+Tab It's a bugger that you cannot edit bugs for corrections :( it is on a form running on my postgresql server. so please provide instructions to extract form for testing.
waiting for instructions on how to send you the form
@Ian To retrieve the XML definition of 'form1', type: SELECT kexi__objects.o_name, kexi__objectdata.o_data FROM public.kexi__objects, public.kexi__objectdata WHERE kexi__objectdata.o_id = kexi__objects.o_id AND kexi__objects.o_name = 'form1'; Then please copy and paste this result to a file, compress and attach below.
Non-interactive use of the psql command - creates the form_definition.txt file: echo "SELECT kexi__objects.o_name, kexi__objectdata.o_data FROM public.kexi__objects, public.kexi__objectdata WHERE kexi__objectdata.o_id = kexi__objects.o_id AND kexi__objects.o_name = 'form1';" | psql new_database postgres -W -A > form_definition.txt
(of course change <postgres> to your username and <new_database> to your db name (not caption, and lowercase is needed)
(and 'form1' should be your form name (not caption))
Created attachment 88658 [details] output from query above, looks like this might be the right thing Ian
Thanks, got it: http://wstaw.org/m/2014/09/11/plasma-desktopjp2613.png
It would be useful to know table that the form is bound to. 1. Retrieve list of field definition, e.g. for 'table1' use: "SELECT kexi__fields.* FROM public.kexi__objects, public.kexi__fields WHERE kexi__fields.t_id = kexi__objects.o_id AND kexi__objects.o_name = 'table1';" 2. Export entire table to a file. 3. Retrieve supplementary schema, just replace 'form1' with 'table1' or so. Please provide results in files.
1. done , output from pgAdmin query and I will attach as field_definition.txt 2. done through kexi as books.csv . I'll send this direct via email 3. not sure if I am with you here. form1 -> table1 form1 was 'data_entry', and we got output table1 must be 'books', so if I read you right SELECT kexi__objects.o_name, kexi__objectdata.o_data FROM public.kexi__objects, public.kexi__objectdata WHERE kexi__objectdata.o_id = kexi__objects.o_id AND kexi__objects.o_name = 'books'; no output generated
Created attachment 88659 [details] fields in table 'books'