Wakanda makes progress – get your razor blades out and make you pretty. Or what tries the message to tell me? See yourself …
4D v12.2 breaks QPix 3.5.7 — solved
[26 May 11] We have uploaded QPix 3.5.8b12 which seems to solve all issues introduced by 4D v12.2. All plug-ins will soon be updated to incorporate the necessary adjustments.
AreaList Pro v9.0 MC1 is available at the following address:
Continue reading →
Helping my workflow
Typeahead ought to support repeating or tedious tasks. I like typeahead very much and my customers do too, when installed and when supporting their workflow. Otherwise I’ll get it in the neck.
Not every kind of typeahead is useful for everybody. The typeahead in V12.2 stopps my workflow more than necessary. I would be better off, having less typeahead, actually.
First I loved the typeahead of 12.0. Now with 12.2 its getting in my way! To me, the current implementation of type-aheads is to much of a theoretical idea than of practical use. I’ll describe some instances.
– Unpractical is inserting the first table between the brackets when writing CREATE RECORD().
+ Practical would be adding the brackets after CREATE RECORD and setting the cursor in between.
– Unpractical is to get nothing after the semicolon of QUERY([Table];
+ Practical would be offering filling up QUERY with (;=) and inserting the cursor in between bracket and semicolon
– Unpractical is to get a list of some hundred tables before typing any letter.
+ Practical would be offering a short list of tables, starting with the entered letter and not earlier.
– Unpractical is counting nested brackets
+ Practical is closing every bracket immediately and moving the cursor back 1 character
Me and many I know have the behaviour of setting opening and closing brackets immediately already in their genes.
I’d appreciate some more consistency.
This looks great, but what is the cursor waiting for then?
I’d like to get the best & practical typeahead
Let’s start a collection: use the comment-section on this page. I’d appreciate a short description of what is unpractical and what would be practical like this:
– Unpractical is
+ Practical is
TWAIN protocol problem solved
In the usual fast and reliable way ESCAPE solved a problem between 4D v12.2 & QPix. 4D v12 stopped recognizing the TWAIN protocol. It worked fine up to 4D v12.1.
Danis Georgiadis released QPix v3.5.8b12 yesterday evening and it fixed the problem.
If you see any problems in your application just contact ESCAPE’s techsupport.