View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003891 | JEDI VCL | 00 JVCL Components | public | 2006-09-09 07:42 | 2007-01-04 01:57 |
Reporter | dzomlija | Assigned To | obones | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | resolved | Resolution | suspended | ||
Product Version | 3.20 | ||||
Target Version | Fixed in Version | ||||
Summary | 0003891: Speed Button Glyphs are white in Windows Vista | ||||
Description | This actually seems to be a bug carried over from the Borland implementation of TSpeedButton, as the bug is visible if either TSpeedButton or TJvSpeedButton is used. The issue is only apparent if the compiled application is run on Windows Vista Beta 2. Status of this error is unknown on Windows Vista RC1. When run on Windows XP, the glyphs on TSpeedButton, TJvSpeedButton, TBitBtn and TJvBitBtn appear as they should. Run the executable on Windows Vista, and the Glyphs are white. This bug does not appear with TJvImgBtn. What I'd like is for an implementation of TJvSpeedButton that uses standard image lists for their glyphs. This is necessary to display correctly on Vista, and because my application requires that input focus is not changed from the current control when a button is clicked. That's why I use TJvSpeedButton. | ||||
Tags | No tags attached. | ||||
2006-09-09 07:42
|
Speed Buttons.zip (290,070 bytes) |
|
Please try with the current SVN version, and if that does not help, then I'm sorry to say that we will NOT fix bugs that are in BETA versions of Microsoft's operating systems. They are by definition a moving target and it might well be that their next beta will have fixed this already. |
|
"then I'm sorry to say that we will NOT fix bugs that are in BETA versions of Microsoft's operating systems" Hmmn.... Then maybe I should stop using JEDI, as it seems you are missing the point altogether. The entire concept of BETA software/operating systems is to give developers such as myself an opportunity to adapt our projects to fix any incompatibilities that may arise with the new architecture. This allows us to provide our users with software that will work as expected in the environments they will be using. See if your narrow minded perception can get past this scenario: The JEDI team releases a BETA of the VCL library in order to gauge acceptance of the product, and to receive feedback about bugs, except no-one uses it because it's a BETA, and wants to wait for the final release. Now, you won't be able to release a final version sooner, because you're not getting any bug feedback. Your resolution to this issue is "won't fix". Personally, I believe it's "can't fix" because you're not willing to give new ideas a chance. Pass this on to another developer. But I'm using this space for a personal attack on you when I shouldn't, but I will not apologise for my criticism of your "professional" behaviour. It's exactly your kind of attitude that will lead to the ultimate failure of Open Source in general. Maybe if I get SourceForge involved, you'd start doing what you're supposed to do... |
|
Ok, then please send me the required amount of money to buy the licence for Vista. Oh wait, I'd have to get an MSDN subscription as well. I'm quite sad you're taking things this way, like we owe you something. You come here, whine about something we cannot reproduce for sound reasons, you did not even start searching on your own despite having all the required tools and you bitch about our reaction? Well, I'm sorry to say that this discourages me from even considering starting to help. |
|
Thank you for your feedback, Obones. My apologies for reacting the way I did. A little uncalled for, perhaps. The manner in which you responded did, however, inspire me to create a solution. So, unless you have any objections, how do I go about submitting my TVnsSpeedButton component as a contribution to JVCL? Peter |
|
Well, if it can be integrated in the existing TJvSpeedButton, yes. The current aim of the JVCL is to limit the number of new components, even reduce the existing ones by grouping them into one. This adds clarity to the whole library. |
|
Well, no news, closing the issue. |
Date Modified | Username | Field | Change |
---|---|---|---|
2006-09-09 07:42 | dzomlija | New Issue | |
2006-09-09 07:42 | dzomlija | File Added: Speed Buttons.zip | |
2006-09-09 08:58 | obones | Status | new => resolved |
2006-09-09 08:58 | obones | Resolution | open => won't fix |
2006-09-09 08:58 | obones | Assigned To | => obones |
2006-09-09 08:58 | obones | Note Added: 0010087 | |
2006-09-09 10:26 | dzomlija | Status | resolved => feedback |
2006-09-09 10:26 | dzomlija | Resolution | won't fix => reopened |
2006-09-09 10:26 | dzomlija | Note Added: 0010090 | |
2006-09-09 13:29 | obones | Status | feedback => closed |
2006-09-09 13:29 | obones | Note Added: 0010092 | |
2006-09-09 13:29 | obones | Resolution | reopened => won't fix |
2006-09-15 13:26 | dzomlija | Status | closed => feedback |
2006-09-15 13:26 | dzomlija | Resolution | won't fix => reopened |
2006-09-15 13:26 | dzomlija | Note Added: 0010134 | |
2006-09-16 06:11 | obones | Note Added: 0010135 | |
2007-01-04 01:56 | obones | Status | feedback => resolved |
2007-01-04 01:56 | obones | Resolution | reopened => suspended |
2007-01-04 01:56 | obones | Note Added: 0010508 |