Strange Stuff with the Gambas editor
Posted
#1
(In Topic #307)
Expert

I've seen nothing on the email list or here on the Forum so have to assume that it may well be a MAMCO.
(Me And My Computer Only).
The concern is that I had this on Ubuntu 18.n and have just recently moved to Mint 19.1 (Tessa) and the effects are the same.
1. The editor will 'freeze' and while I can move the cursor, I just can't edit any text at all.
This is random and I can go a long session without this happening but will occur 2-3 times in another session.
The simple fix is to save all and restart the editor and it's all working again.
It's random as far as I can see. I'm not doing anything special but it is possible that a sequence of events triggers this but I've not been able to determine what they are.
2. When I copy and paste code in a form that I'm working on; this can be any class or module code where I paste anything from a couple of lines to multiple subroutines.
I will get a ghost paste of what is normally the last function/sub block of code minus the declaration header at the end of the code page.
One or both of these events can happen in a tiny single form project or a quite large (5 Modules, 30+ Classes and Forms) and I do some long sessions with 4-8 hours not being uncommon.
I was wondering if anyone else had experienced these symptoms before and if they had a fix or at least knew what series of events triggers the behaviour.
Cheers - Quin.
I code therefore I am
I code therefore I am
Posted
Regular

On my Mint 17 Mate machine, occasionally, and very occasionally, clicking the mouse in the edit area is ineffective. The solution that seems to work is to click somewhere else outside of Gambas, then click again in the edit area.
.... and carry a big stick!
Posted
Expert

The one other thing I noticed about the Gambas implementation on Mint is that TextBox backgrounds are no longer white by default but are form background(?) colour.
If you change them manually, you still get a ugly border of the original colour a few pixels wide.
I'll try the QT5 solution you tried and see if that helps.
For the editor freezing, I think I've tried cvlicking outside the editor but I'll grasp any straw offered and give that a go next time.
Thanks mate.
Quin.
Cheers - Quin.
I code therefore I am
I code therefore I am
Posted
Trainee
Posted
Regular

Posted
Expert

I've never had much luck with the GTK component either
I found another strange behaviour yesterday when using the colour button control.
New projects just used the Gb.gui (QT/GTK Switcher ) which is the standard component for such I think.
Placed a colour button on the form I was working on and did some testing.
Clicking on a colour button at run time automatically opened a simple colour selection dialogue.
The one with the circle and the internal triangle for changing the required colour but once selected,
the displayed colour of the button did not change nor could I set it manually by setting the Color/Value
properties.
I change the component in project properties from GB.GUI to Gb.gui.qt.
Now clicking on the colour button opens a different more complex colour selection dialogue and also sets the colour of the button correctly. Also, now setting the colour of the button manually displays the correct colour.
Same outcome when swapping to the Gb.Qt4 component.
Unless someone smacks me up the back of the head and says "you're just doing it wrong"…. which is quite possible, then I'll send something to the Gambas mailing list for investigation.
Cheers - Quin.
I code therefore I am
I code therefore I am
Posted
Administrator

Quincunxian said
Hi cage,
I've never had much luck with the GTK component either
I found another strange behaviour yesterday when using the colour button control.
New projects just used the Gb.gui (QT/GTK Switcher ) which is the standard component for such I think.
Placed a colour button on the form I was working on and did some testing.
Clicking on a colour button at run time automatically opened a simple colour selection dialogue.
The one with the circle and the internal triangle for <COLOR color="#FF0000">changing the required colour but once selected, the displayed colour of the button did not change nor could I set it manually by setting the Color/Value
properties</COLOR>.
I change the component in project properties from GB.GUI to Gb.gui.qt.
Now clicking on the colour button opens a different more complex colour selection dialogue and also sets the colour of the button correctly. Also, now setting the colour of the button manually displays the correct colour.
Same outcome when swapping to the Gb.Qt4 component.
Unless someone smacks me up the back of the head and says "you're just doing it wrong"…. which is quite possible, then I'll send something to the Gambas mailing list for investigation.
Same issue with a TextEdit using QT5 component.
Posted
Regular

I change the component in project properties from GB.GUI to Gb.gui.qt.
Now clicking on the colour button opens a different more complex colour selection dialogue and also sets the colour of the button correctly. Also, now setting the colour of the button manually displays the correct colour.
Same outcome when swapping to the Gb.Qt4 component.
Unless someone smacks me up the back of the head and says "you're just doing it wrong"…. which is quite possible, then I'll send something to the Gambas mailing list for investigation.
The only thing I will smack would be a pat on the back. The Gb.gui.qt solves all the problems with color at least on buttons and text boxes and text editor. Really nice find
Posted
Regular

1 guest and 0 members have just viewed this.

