PureBasic 4.41 is released !

[milan1612]

@PB-Team: ...what I don`t understand: Fred fixed a lot today...Why didn`t you wait for releasing 4.41 a few days?

I guess there has to be a border between two versions

[Kuron]

@PB-Team: ...what I don`t understand: Fred fixed a lot today...Why didn`t you wait for releasing 4.41 a few days?

You might want to wait for the bug fix for 4.41

[freak]

@PB-Team: ...what I don`t understand: Fred fixed a lot today...Why didn`t you wait for releasing 4.41 a few days?

Just wait for the next release if we are too fast for you.

[Fred]

We just don't know when we will have time to do a bug fix session. So toady it was one, the fixes will be included in the next release.

[Michael Vogel]

@PB-Team: ...what I don`t understand: Fred fixed a lot today...Why didn`t you wait for releasing 4.41 a few days?

Let Fred keep running

Whatever he've got to breakfast this morning, he fixes and fixes and fixes... (seems that Fred tries to beat an olympic record in marathon bug fixing, in Vancouver he might get problems with the WADA)

Thanks for all your efforts, Fred, go for gold !

[Blue Steel]

Because they are doing fixes juyst about EVERY day. who knows when they get a bright idea on how to fix problems. If they were to wait till they ran out of ideas to release it we'd be waiting forever. its best to get the bug fixes out ASAP in my opinion so I welcome ANYTIME there is a new Release and I don't knock it. Its always been a problem for developers of anything .. "When should i release" Fred has chosen this method and its working ok

(What i'd really like to see are like nightly builds put out there for those who want to test the bugs / fixes prior to the releases. this way those who want to be on the bleeding edge can be and those who want the latest tested release can get which ever they want)

@PB-Team: ...what I don`t understand: Fred fixed a lot today...Why didn`t you wait for releasing 4.41 a few days?

[Ramihyn_]

Just wait for the next release if we are too fast for you.

We just don't know when we will have time to do a bug fix session. So toady it was one, the fixes will be included in the next release.

What will that next release be? 4.42? or 4.50?

[Fred]

Who knows ?

[Ramihyn_]

Who knows ?

Well i will explain why this is important to me.

I am currently praying that my app won't be affected by this bug: http://www.purebasic.fr/english/viewtop ... =4&t=40921

It was fixed, but the bugfix will be "in the next release". If the next release will be 4.50, it will take 8 to 9 months reliastically and i will have to wait for the bugfix on that, which will mean 9 to 12 months from now on. I already gave up on PB once before, because the bugs just didnt get fixed for wayyyyyyyyy tooooo looong*. I asked for bugfix releases "in between" back then, but only got a reply in mail that "we dont have the resources to do that".

Now i was glad to see that the policy was changed and the bugfix releases where introduced with 4.31 and 4.41, so i keep waiting for those. So now i wonder if i can

• - write my own cross-portable listicon gadget
  - go back to 4.31 and undo all alphachannel changes i did for 4.4x
  - hope that either in the beta directory a fix will appear or a 4.42 will be released while telling a lot people which are waiting for a new software release - that it could take another year to appear

Who knows ?

You probably dont realize what kind of strong signal against commercial use of PB you are sending out here, by basically saying "a fix for a new bug introduced in the bugfixed release, might just take a year. so what?"

And while netmaestro was right that we may not even get a fix, because mixing API flags with PB controls is not supported, the problem is that PB simply doesnt support some widely used common things which customers expect in a software. You (the software developer having to deal with customers/companies) just look damn stupid if for example you tell a customer that you cant do modal requesters in windows in 2010, so you are forced to use API flags with PB controls at some places.

Maybe you see my point even though this might sound like a harsh rant to you, sorry



* actually thats wrong, the bugs where fixed, but the fixes wheren't released to the customers for months.

[UserOfPure]

You just look damn stupid

Yeah, that's gonna get the team listening to you in future. :roll:

[Ramihyn_]

You just look damn stupid

Yeah, that's gonna get the team listening to you in future. :roll:

That "You" was refering to the software developer who has to deal with end customers/companies and not refering to Fred and the PB Team. Sorry if it was phrased in a way which made it misunderstandable - i will try to choose a better phrase, but english isnt my first language.

I dont intend to insult anybody here, sorry.

[Kuron]

What will that next release be? 4.42? or 4.50?

If you need to, downgrade to a previous version that does not have the issue you are experiencing.

[Fred]

The release cycle is now faster, which means you won't have to wait 9-12 months to get the fix, but probably 4 before the new release is out. We can't do several small release, it's just suck up too much time for a small team like us.

Now, my short reply was kind of joke (we usually don't talk about future plans for good reasons), if you can't understand that, just ignore my post. No needs to rants like that on a that small issue.

[Trond]

so you are forced to use API flags with PB controls at some places.

No, you are never forced to do that. You can use an API message requester, and it should work. The same with an API listicon. You don't have to use PB. It's your own free choice. You could switch to C, but then you would have no listicon available at all (unless you use an API one, which you can do in PB as well).

[Kuron]

so you are forced to use API flags with PB controls at some places.

Yes, you can use SDK programming with PureBasic if you choose to.

PB is cross-platform, in order for PB's native support of "gadgets" to work properly on all OSes, PB can generally only support the gadget features that work on all platforms. This is not necessarily restricted to cross-platform programming languages. Languages that are Windows only can have the same restriction if you are targeting multiple versions of Windows, as on older versions of Windows controls (gadgets) do not necessarily have the same features and functionality as on newer versions of Windows.