Ok, so I'm going to try something new here. I'm not certain how well it will work, what sort of feedback I'm going to get, and whether I'll even follow thru with my idea.
There are times when I need to shut my brain down (so to speak) and work on simple to fix bugs. These are usually cosmetic issues such as "the color of such and so is wrong" or "bleh is 2 pixels too wide". Basically, things that take < 5 minutes to fix.
So here's where I try something new. I'm going to give a list of requirements, and you're going to provide a list of bugs that meet them, and then I'll put those on my "little annoyances to fix at a whim" list (which resides solely in my brain).
I'm hoping that this is an easy way for me to get targeted testing, and for everyone to get a more stable product. I figure that in time I'll switch the current bug list requirements to other topics.
General Requirements:
1. The bug must be in the bug base. If you do not post a bug ID number with your description, it'll be ignored.
2. The bug must be always reproducible. If it's the sort of thing that happens every once in a while, it's probably not easy to fix.
3. The bug must be a small bug and *not* a feature request. If you start posting pet bugs like "fix RBScript" or feature requests like "Please implement X, it's quick!", it's going to be ignored.
Current Bug List Requirements:
1. Only submit cosmetic framework issues.
2. Do not submit any bugs with the IDE unless the IDE shows the cosmetic framework issue.
3. Only submit bugs about Windows. If it's cross-platform, that's fine. But if I can't reproduce it on Windows, it's ignored.
If I see a lot of people breaking any of these requirements, I'm going to stop the experiment.
It should be noted that even if you report a bug via the feedback system and discuss it here, I have the final say in whether it's a quick and easy bug fix or not. If I say it's hard, then it's hard and it stays in the normal queue. Furthermore, just because it gets discussed here does *not* (under any circumstances!) constitute a promise that the bug will be fixed. It's just a list of quick bugs for me to work on when I have the time.
Let's see how this little experiment works! Hopefully well....
Whooo Hoooo!
You may eventually regret this but I'll be the first to "bug" you...
I already noted this one in a previous post that was long since stale so since it's high on my list of aggravations I'll risk being daft and post it here with a the bugID and description (complete with a website link to illustrate my plight).
The IDE does not remember it’s previous position on the screen. Despite having maximized it in the previous session it always defaults to the same spot (which happens to be underneath my quicklaunch bar). So then I have to coax it out from beneath the QL bar like a frightened kitten from underneath a bed - EVERY MORNING!
This is one of those “unimportant†bug fixes that slowly begins to wear on a persons nerves. It almost seem to be mocking me with every startup. Anyway I have posted a screenshot of my desktop with the IDE in the offending position (yep just fired her up and there it is)…
http://www.psychjoe.com/Pages/desktop.htm
Notice that I have access to the file menu but the Titlebar is under the quicklaunch bar(s) - I'm actually using two (I like it because I never have to use the Start button - everything is accessible from the bar)
Here is the bug ID - tizjyiar
If you need anything else let me know (I might even rub your shoulders [in a purly manly fashion] whilst you fix my bug)
;-)
~joe
You get an E for effort, but a B for bad. See current rules #1 and #2. Yes, it's a bug, but it's not in the category of bugs I'm trying to target.
That being said, if it were on "topic" (so to speak), it's an excellent example of the style of impromptu reports I'm looking for.
I read those rules so I must assume that I don't understand what a cosmetic framework bug is...
~joe
Oh! Well then I should probably explain instead of chastising. :-)
Framework bugs are ones that affect your built applications, and cosmetic ones are small, visual-type glitches. For example:
1) The inactive highlight color on a listbox is supposed to be light grey on Windows, but it is dark blue in RB (currently fixed, btw).
2) The pushbutton which currently has the focus should respond to the Enter button being pressed (also fixed).
3) The documented system font should be Tahoma for Win2k and up instead of Ms Sans Serif.
Things like that are examples of cosmetic framework issues.
Got it!
I don't have any of those because I'm generally not as concerned with how *my* application looks - as I am with how yours looks
:^)
~joe
LoL, well, eventually I'll put up a call for IDE bugs I'm sure. I'm just making the framework ones as a trial run since everyone likes it when their programs work a little better or look a little more right.
Here is one, but it breaks your "reproducible on Window" rule but it is a Windows only issue:
mtyaobpi
That is the one I reported earlier about apps compiled on the Macintosh only display the Windows icon in 8-bit. I would *love* to see this one fixed, and since you say that 32-bit icons work correctly on Windows I hope this one is something easy to fix.
Again I am going to break your rule and put in a Feature Request... but I personally think this is so easy I don't know why it hasn't been added already -- an Invisible cursor:
qzvcneka
Don't you just need to copy the resource of an exisiting cursor, delete the pixels and rename it to "InvisibleCursor"?
Having an invisible cursor will mean that I can draw whatever I want at the cursor position in the target canvas -- including 32-bit style cursors. Think of Photoshop where each tool has a different cursor and the option brush size (which is usually much larger than the 16x16 cursor size).
We're just a bunch of outlaws Aaron!
Rules? Rules? We don't need your stinkin rules!
;-P
~joe
Unfortunately, this little experiment isn't turning out quite like I had hoped. 10 posts and none of them are in the category I wanted. :-P
Hey Joe,
As a workaround you could right click the shortcut icon that you use to start the IDE and choose Properties. Then on the dialog that comes up, choose the Shortcut tab. In the dropdown entitled Run, choose Maximized. That might make it less annoying.
Scott
http://www.realsoftware.com/feedback/viewreport.php?reportid=tsjvqbaw
Scrolling a listbox horizontally doesn't look very good.
Here is a sample project to demonstrate the bug (the bugbase won't let me attach it after I submitted it): http://amazon.wolfire.com/listboxhorizscrollingexample.zip
http://www.realsoftware.com/feedback/viewreport.php?reportid=pjjcymke
Listboxes with large headers look kind of odd in the IDE. See the same sample project: http://amazon.wolfire.com/listboxhorizscrollingexample.zip
http://www.realsoftware.com/feedback/viewreport.php?reportid=asnmhpkg
ctrl-shift-] and ctrl-shift-[ don't do anything - they should be listed as ctrl-tab and ctrl-shift-tab
http://www.realsoftware.com/feedback/viewreport.php?reportid=jtitlejb
scroll bars appear when they don't need when dragging windows around the window editor
The first link you provided is the only one that matches the criteria. The rest are IDE bugs.
I realized my mistake when I re-read the original post. :( I don't really care about any of the other bugs except for the first one, just trying to help.
It's fine, I'm just pointing it out, and I do appreciate the help. :-)
Canvas - StaticText Controls on the Edge of a Scroll Canvas Draw Outside Of Its Bounds
http://www.realsoftware.com/feedback/viewreport.php?reportid=rbcysihh
Same occurs with GroupBoxes and ListBoxes which gets REALLY annoying because they're so big!
I'm only guessing that this affects Windows as well... I really don't like that last requirement :^p
In a bid to encourage people to follow my meager rules a little better.... Jeff (the person who followed the rules on at least one report!) got his bug fixed. Nya nya nya and stuff. :-P
I suppose, but mine was fixed too (by Scott's sage advice).
So put down one for the bandits!
It's the bottom of the second day and the game is tied 1 to 1...
~joe
You gave us a hard task.
Personally, I spend only about 10% of my time on Windows (about the exact opposite of you Aaron?). So I do not feel that I am qualified to find the issues you are referring to. Sure if I run into something, I will report it, but there are very few specific problems I have run into with REALbasic and MS Windows.
Well, I kinda wondered whether I had picked the wrong target audience with this one. But I figured that since I deal with mostly Win32 issues in RB (when there's any one platform involved), more of my readers would be Win32 people.
If this is still opened here are two:
If you try to resize a WebBrowser control in code, it does not get resized:
http://www.realsoftware.com/feedback/viewreport.php?reportid=ujuclotx
WebBrowser or HTMLViewer "disappears" when resizing window:
http://www.realsoftware.com/feedback/viewreport.php?reportid=evxlsqvz