Not many people care about “likes” or “doing their duty” as they either don’t see the point as things languish for multiple years with no fix while other less “liked” bugs and features are fix/implemented.
The way around it (I hate providing work arounds as it tends to mean xojo will never fix the thing) is to paste, move the whole selection to the side of the window, change tabs, then move it all back in which is just terrible.
Or users have other things to do than liking all issues that might be important to them. Personally, I don’t spend hours everyday in listing all the issues in the system to find the ones that concern me for liking them; would be too time consuming.
In other words, I don’t think the current system of only fixing “liked” bugs is the right approach.
I know it’s a pain to discover that. My workaround, which I learned from a forum post, is to use containers to do the layout, then drag the container to the appropriate tab. Next, duplicate the container and copy the duplicate to the new tab. Using this approach has the added benefit of allowing the selection of multiple controls with your mouse for editing or moving into position.
I wanted this changed several years ago as I have several issues that will never get enough “likes” to get resolved. I tried to open a discussion with Xojo about other possibilities, but it never went anywhere.
I keep seeing complaints about currency type.
Never used one, never will. So I’ll never bother upvoting such a bug, yet I understand it is pretty critical.
Now and then at one place I was coding, we would have a ‘trivial week/few days’.
Literally going through the bugs that were low priority yet obviously ‘10 minute fixes’.
(eg Something is the wrong color… wrong number of decimals… incorrect spelling…)
We could flatten 500 bugs in a week, and the result was happier customers because they could see things getting done.
By restricting it to a sprint, few people complained that ‘big issues’ were ignored.
It just cleared some of the fog from the issues list.
Just imagine a severe bug is in Xojo, which is reported in Issues, but no one takes time to “like” it (various reasons are possible, like the users who usually “like” things happen to be the ones with which this issue don’t apply). So Xojo wouldn’t fix an important bug, but fixes the liked ones; the criteria to fix bugs isn’t logical.
Now, if even that fact must be passed to a MVP to be taken into account, it’s hopeless.
I think the “Bug Bash”, while not the same as your ‘trvial week/few days’, helps achieve some bugs getting attention that otherwise may not qualify for action. And lets us help promote things to their attention. I hope we continue to see more “Bug Bash” intervals.
I finished minutes ago and I am nearly happuy with that, now.
How do you go to the other Tab ? (sometimes, most of the time ?)
Click in a Control may reveal the tabs (in my case Importation and Exportation). I stayed minutes contemplating the invisibles tabs, then stand up to drink a Pespi Cola, and resume coding: a click in the Navigation pane…
This bug is not two or three years old… my memory fails, but I think it is far older…
At last, I falled into another bug: my export generated an infinite loop on the… first Record (saves endlessly the same first Record from the SQLite db in the target .csv file). Time to sleep (this night)
Then, minutes ago, I realized my “Do” line is misplaced (before the RecordSet Query !). A simple Cut / Paste and the export is done and works fine, now.