Hi Boki,
There are two small glitches in the program:
1. When the program runs the most left column looks filled with info from bottom forms canvases
2. When a checkbox is selected and when adding rows in one moment the last checked cell becomes highlighted (blue)
See the video below
NextGrid behavior.wmv 304.48KB
9 downloads
Best regards,
Luben
- Berg Forum
- → Viewing Profile: Posts: Luben
Community Stats
- Group Members
- Active Posts 116
- Profile Views 8,708
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Not Telling
Posts I've Made
In Topic: NextGrid v6 - First Demo
21 December 2012 - 08:28 AM
In Topic: NextGrid scroll bars misbehavior
20 December 2012 - 11:05 PM
Hi Boki,
I think that I located the problem - it's something wrong happening during the NextGrid initialization (Create) in Frames. The following facts confirm my observation:
1. Frames don't have OnCreate event, it should be artificially made by overriding manually the constructor Create
2. In the Frame OnCreate (see 1) procedure if I add rows in NextGrid the scroll bars appear (manifestation of the problem)
3. If in the main form where the frame was placed I manually Reset the NextGrid (NextGrid.ClearRows) and add the rows - everything becomes alright - see the attached video below
Scroll Bars.wmv 245.23KB 2 downloads
In short - if the grid was initialized in the main form (not in the frame) - the problem is not there.
Best regards,
Luben
I think that I located the problem - it's something wrong happening during the NextGrid initialization (Create) in Frames. The following facts confirm my observation:
1. Frames don't have OnCreate event, it should be artificially made by overriding manually the constructor Create
2. In the Frame OnCreate (see 1) procedure if I add rows in NextGrid the scroll bars appear (manifestation of the problem)
3. If in the main form where the frame was placed I manually Reset the NextGrid (NextGrid.ClearRows) and add the rows - everything becomes alright - see the attached video below
Scroll Bars.wmv 245.23KB 2 downloads
In short - if the grid was initialized in the main form (not in the frame) - the problem is not there.
Best regards,
Luben
In Topic: NextGrid scroll bars misbehavior
18 December 2012 - 06:04 PM
Hi Boki,
I found something bizarre - I managed to fix the problem but I feel that something is wrong. In short:
1. I have a main form with multiple tabs (NxPageControl)
2. I have multiple frames, each frame is used only once in the main form. There are multiple components on each frame, including NextGrid tables
3. In the frame where the problem grid resides there are several NextGrid, only one is misbehaving.
4. I found that if I delete all columns in the problem grid on the main form (but not touching the columns in the frame) the problem disappears.
In short - if I delete the columns in the frame implementation (frame placed on the form) the grid is OK.
BTW I found before that if I delete / add NextGrid columns in the main form (but not touching the frames) sometimes the column description remains in the class declarations. The result is - when you add in the form or in the frame a column and if by accident it has the same name as the remained one an error message pops up. The solution is to manually delete this column.
I guess it's something connected with the frames
Best regards,
Luben
I found something bizarre - I managed to fix the problem but I feel that something is wrong. In short:
1. I have a main form with multiple tabs (NxPageControl)
2. I have multiple frames, each frame is used only once in the main form. There are multiple components on each frame, including NextGrid tables
3. In the frame where the problem grid resides there are several NextGrid, only one is misbehaving.
4. I found that if I delete all columns in the problem grid on the main form (but not touching the columns in the frame) the problem disappears.
In short - if I delete the columns in the frame implementation (frame placed on the form) the grid is OK.
BTW I found before that if I delete / add NextGrid columns in the main form (but not touching the frames) sometimes the column description remains in the class declarations. The result is - when you add in the form or in the frame a column and if by accident it has the same name as the remained one an error message pops up. The solution is to manually delete this column.
I guess it's something connected with the frames
Best regards,
Luben
In Topic: NextGrid scroll bars misbehavior
18 December 2012 - 02:37 PM
Hi Boki,
The grid is placed on TFrame, DoubleBuffered was set to False both to frame and the grid.
It looks like there is some hidden, private variable that holds the memory of this misbehavior - once the grid "switches" in this mode there is no way to return it back. The solution is - delete the grid and redesign it from scratch. I'll try to gather more information how and when the problem appears.
BTW, I always keep doubleBuffered to False, setting it to True yields multiple problems
Best regards,
Luben
PS
I found that setting HideScrollBars to False hides the horizontal bar
1. HideScrollBar = False
With hideScrollBars.png 4.04KB 0 downloads
2. HideScrollBar = True
HideScrollBars to True.png 5.43KB 0 downloads
The grid is placed on TFrame, DoubleBuffered was set to False both to frame and the grid.
It looks like there is some hidden, private variable that holds the memory of this misbehavior - once the grid "switches" in this mode there is no way to return it back. The solution is - delete the grid and redesign it from scratch. I'll try to gather more information how and when the problem appears.
BTW, I always keep doubleBuffered to False, setting it to True yields multiple problems
Best regards,
Luben
PS
I found that setting HideScrollBars to False hides the horizontal bar
1. HideScrollBar = False
With hideScrollBars.png 4.04KB 0 downloads
2. HideScrollBar = True
HideScrollBars to True.png 5.43KB 0 downloads
In Topic: NxSpinEdit shows button
05 December 2012 - 07:36 AM
Hi,
Probably setting the button position outside of the visible canvas can solve the problem.
As I said during run time there are no problems but you'll be very worried if you load an old project and you see completely different view of the NxSpinEdit components. The design time is following the principle - "what you see is what you get", here you see one picture in design time and different in run time and of course this yields problems.
Imagine that you have on the form 100 NxSpinEdit controls and half should display the button and half should be without button and to make things worse all controls are shuffled. To check is it everything alright you need in design time to visit the Property inspector of each component instead of throwing a look at the form. Notice that it's not always possible to run the whole application in order to check the NxSpinEdit were set correctly - for example if a team of programmers is working separately on different forms or if there are multiple mistakes in the source.
My point is - in some cases this visual glitch could turn into a boring "feature".
Best regards,
Luben
Probably setting the button position outside of the visible canvas can solve the problem.
As I said during run time there are no problems but you'll be very worried if you load an old project and you see completely different view of the NxSpinEdit components. The design time is following the principle - "what you see is what you get", here you see one picture in design time and different in run time and of course this yields problems.
Imagine that you have on the form 100 NxSpinEdit controls and half should display the button and half should be without button and to make things worse all controls are shuffled. To check is it everything alright you need in design time to visit the Property inspector of each component instead of throwing a look at the form. Notice that it's not always possible to run the whole application in order to check the NxSpinEdit were set correctly - for example if a team of programmers is working separately on different forms or if there are multiple mistakes in the source.
My point is - in some cases this visual glitch could turn into a boring "feature".
Best regards,
Luben
- Berg Forum
- → Viewing Profile: Posts: Luben
- Privacy Policy