Thx for the replies people.
I've checked and I don't believe I have done this wrong:-* Child widgets are created outside their parent's xywh boundaries
I'm working on reducing your app so it'll compile without the
.cpy stuff.
You do have to watch out for things like this:
win2_tabs = new
Fl_Tabs(x,y+25,x+400,y+200);
win2_grp1 = new
Fl_Group(x,y+50,x+400,y+200,"Transaction");
If you look closely, you'll see that the win_grp1's height is
too large
for the parent; its 'y' position is 25 pixels lower than the
parent, but the
height is the same, which means it'll extend 25 pixels beyond
the bottom
of the parent win2_tabs.
To fix the above you'd use instead:
win2_tabs = new
Fl_Tabs(x,y+25,x+400,y+200);
win2_grp1 = new
Fl_Group(x,y+50,x+400,y+200-25,"Transaction");
I haven't checked the code yet, still working on reducing the
code
to just the GUI code, so it'll build.
On Friday, October 7, 2022 at 11:57:12 AM UTC+11 roger tunnicliffe wrote:
Thanks for your effort (not sure your name)
I think you will struggle without the copy files so here they are..
On 10/6/22 19:33, roger tunnicliffe wrote:
Thx Greg.Yes, win2_accountNoX was an effort to produce an alphanumeric spinner (I couldn't find one in fltk, I guess you could tell me if there is one).
No spinner for alphanumerics, if I understand you correctly.
Fl_Spinner AFAIK is numeric only.
You can of course make a custom composite widget that derives
from an Fl_Group with two up/down buttons around an Fl_Input
widget,
the up/down buttons invoke a callback that handles cycling the
alphanumerics in the way you want, and you can provide methods
that get/set the value. Fl_Input would both show the value and
also
let someone just go ahead and type it in.
If that sounds useful we can advise, just describe how the
alphanumeric
aspect should work.
It's be best if for this thread if you could reduce the app to
just the FLTK
code, without the non-FLTK stuff to demo the problem. So if
the problem
ist just with the win2 window's widgets, and the menu items
aren't important,
then reduce the test app to just that, so anyone here can
build and run.
It did not display too well as you have noted but this morning I have re-coded that withwin2_accountNo->color(0xE1E1E100);
win2_accountNo->textcolor(0xE1E1E100);
which hides the the numeric value nicely.
On 10/7/22 16:14, roger tunnicliffe wrote:
Thx Greg,I now have a bare bones program that will highlight the problem.Line 63 is where my "timer" is. If you leave it commented out then the win2 spinner will show a single "a".press the up or down and you will be shown "aaaaa"
I would image that, depending on the speed of your system you may need to adjust the 1,000,000 times I have used.
As I said, unless you are just plain curious I wouldn't sweat over this. I am happy use the numeric spinner as I am really just developing this so that I can build the interface to languageONE.