Re: Preemptive mode flaw

[David Adams via 4D_Tech]

> I'm curious to know in which one of my postings you have found the
following sentence
> "that basic error checking is a weird thing to worry about".

No, not your words - my paraphrase. Since my entire point was about error
trapping and you objected, I didn't know how else to interpret your
opinion. It really wouldn't be hard to agree with me:

"Yes, 4D should trap for bad code coming into a worker and report it in a
way that the developer can manage. 4D should not silently destroy the
worker, lose its context, and restart it without reporting the error."

If you agree, we have no dispute. If you disagree, I guess I don't know
what your position is. If you agree, you (and others) can vote for the
feature request here:

http://forums.4d.fr/Post/EN/19391591/1/19391592

Miyako posted an excellent technical analysis (as he always does!) that may
make it possible to reduce the scope of the error request, at least
internally. I don't care about the details so long as we can catch errors
and prevent 4D from killing the existing worker context, showing error
screens, starting duplicate "unique" workers or any of the rest of it.

On the technical front, this issue is most important with CALL WORKER when
the worker is preemptive. According to the documentation on CALL WORKER:

"...they have been designed mainly for interprocess communication in the
context of preemptive processes"
http://doc.4d.com/4Dv16/4D/16.1/About-workers.300-3374909.en.html

Since this is the primary reason the feature was created, it seems entirely
reasonable that it work in a predictable, reliable, and
thoroughly documented manner. Likewise, every effort should be made to help
the developer to use these commands correctly, which includes
systematically and consistently catching and reporting on errors. This is
particularly true since both workers and preemptive mode are new features. I

> I prefer to see the glass half full than half empty,

Absolutely! I am also a glass half-full person. But then again, neither of
us has said what we think the glass is half full *of* ;-)
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Preemptive mode flaw

[JPR via 4D_Tech]

[JPR]

Hi David,

> I find it deeply disturbing that a representative of 4D France somehow
> thinks that basic error checking is a weird thing to worry about

I just would like to correct this:

- I'm not a representative of 4D France, just a contractant.

- I do not talk in the name of 4D in general. I just express my own feeling (or 
opinion), like you do yourself. This feeling is just based on my own experience.

- I do not pretend to detain the absolute truth, and, during trainings, I 
always say that I recommend to do so and so, and never say that this is the 
only way.

- I'm curious to know in which one of my postings you have found the following 
sentence "that basic error checking is a weird thing to worry about".

I prefer to see the glass half full than half empty, this is my way of 
thinking, because I think it's a more positive way. But, here also, I just 
express my opinion, and you're perfectly right to think the contrary. This is 
the way things are going on, because thread springs light. (De la discussion 
jaillit la lumière. — Charles Monnard)

And, as my friend Thibault was used to say: "Progressons! - Spinoza"  (Let's 
get forward!)

My very best,

JPR

> On 08 May 2017, at 19:27, 4d_tech-requ...@lists.4d.com wrote:
> Date: Tue, 9 May 2017 09:04:56 +1000
> From: David Adams 
> To: 4D iNug Technical <4d_tech@lists.4d.com>
> 

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D Write Pro Interface component

[Wayne Stewart via 4D_Tech]

Yes but the ruler is an R feature.

You won't see that in a dot release until 17 dot 0

Wayne


On Tue, 9 May 2017 at 13:01, John Baughman via 4D_Tech <4d_tech@lists.4d.com>
wrote:

> That’s interesting. I am running v16.1 and it is not in the Property List
> as depicted in the blog post. Did it not make the cut for v16.1? I am
> assuming the 16.1 is a later release than 16R2.
>
> John
>
>
> > On May 8, 2017, at 4:28 PM, Keisuke Miyako via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
> >
> > the 4D Write Pro feature "horizontal ruler" was added in 16R2
> > http://blog.4d.com/4d-write-pro-horizontal-ruler/
> >
> >> Anyone know how to get that ruler to show?
> >
> >
> >
> >
> > **
> > 4D Internet Users Group (4D iNUG)
> > FAQ:  http://lists.4d.com/faqnug.html
> > Archive:  http://lists.4d.com/archives.html
> > Options: http://lists.4d.com/mailman/options/4d_tech
> > Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> > **
>
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **

-- 

Regards,

Wayne


[image: --]
Wayne Stewart
[image: http://]about.me/waynestewart

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D Write Pro Interface component

[John Baughman via 4D_Tech]

That’s interesting. I am running v16.1 and it is not in the Property List as 
depicted in the blog post. Did it not make the cut for v16.1? I am assuming the 
16.1 is a later release than 16R2.

John


> On May 8, 2017, at 4:28 PM, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> the 4D Write Pro feature "horizontal ruler" was added in 16R2
> http://blog.4d.com/4d-write-pro-horizontal-ruler/
> 
>> Anyone know how to get that ruler to show?
> 
> 
> 
> 
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D Write Pro Interface component

[Keisuke Miyako via 4D_Tech]

the 4D Write Pro feature "horizontal ruler" was added in 16R2
http://blog.4d.com/4d-write-pro-horizontal-ruler/

> Anyone know how to get that ruler to show?




**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Does anyone know how IP sets and named selections are meant to interact with workers?

[David Adams via 4D_Tech]

I realized after posting that the forums in France are a better place for
my question. If anyone is reading the archives and wants to see if an
answer came through, go to this thread:

IP sets and named selections in workers: What should we expect?
http://forums.4d.fr/Post/EN/19400576/1/19400577
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Does anyone know how IP sets and named selections are meant to interact with workers?

[David Adams via 4D_Tech]

Continuing on with basic research here as the answer doesn't seem to be in
the docs (?)

Workers don't allow for IP variables/arrays, but do allow for virtually
every other thing that you can have in a normal process. You don't get IP
vars, but you do get CALL WORKER. Fine by me. But then I wondered "what
about IP sets?" I guessed that an IP set or named selection created outside
of a worker would not be visible within a worker. I was wrong.

I did a five-minute scratch database and tested out:

* Create an IP set in a standard process (process 1 or a new process, same
results).

* Call a worker and tell it to run a method that uses the set or named
selection and report how many records there are.

The worker saw the IP set and IP named selection just fine.

I have no problem with this - I think it's a good result - but i didn't
find any documentation on the feature one way or the other. Is this
something that we can count on, or is it something that might change in
future versions? We can pass in sets and selections via data without
relying on IP sets/named selections...but I wouldn't go to the trouble
unless I have to.
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D Write Pro Interface component

[John Baughman via 4D_Tech]

Thanks John,

At this point I am not sure what the component brings to the table. 
Opening the component I see that it is using the 4D Write Pro Widget that is 
available i the library without the component.

When I open my database with the component in the component folder, I 
cannot see any of the component methods or forms. As you suggested Icreated a 
subform, but WP_Pallette is not listed under Detail Forms. I tried using the 
component as received as well as built.

None of the links suggested thus far discuss the component. They all 
talk about creating your own user interface or the widget, but not about the 
component. I must not have the component installed properly. 

The widget appears to do nearly everything I would have expected from 
the component. Can’t see what more the component could do or does.

In the LRP under “Defining a 4D Write Pro area” it mentions talks about 
the widget. There is a picture of the widget in use and above the document is a 
ruler. Anyone know how to get that ruler to show?

John

 


> On May 8, 2017, at 11:18 AM, truegold via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> Sigh,
> 
>> My assumption (unproven as I am looking for the same insight)…
> 
> Sorry I’m not sure if this example uses the component or not.
> 
> But I did find...
> 
> http://blog.4d.com/4d-write-pro-user-interface/
> 
> Yes, just create a subform container and then in the Subform properties 
> select “WP_Palette” as the detail form.
> 
> Then the rest I leave to your discovery.
> 
> John…
> 
> 
>> Hi,
>> 
>> I’d take a look at this 4DBlog “ Create your own interface for 4D Write 
>> Pro”. There is an example database you can download. My assumption (unproven 
>> as I am looking for the same insight) and found this v16 HDI example.
>> 
>> http://blog.4d.com/create-your-own-interface-for-4d-write-pro/
>> 
>> And I’m sure then it might make sense of how to use the component.
>> 
>> Hope that helps,
>> John…
>> 
>>> Can someone point me to instructions on how to use the 4D Write Pro 
>>> Interface component.
>> 
> 
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Preemptive mode flaw

[David Adams via 4D_Tech]

Well, I've answered your various points but, overall, I'm disappointed that
you've again failed to offer any actual technical content. Perhaps Thomas
Maul would contribute? He often does not agree with me, but his arguments
are always well-reasoned and technically interesting. Even if Thomas scolds
someone, it's after providing good information.

I also think it may be too easy to get caught up in how cranky I sound. So
I sound cranky, so what? That's more my problem than anyone else's. Does it
make me or my arguments more convincing when I sound like that guy on the
bus that no one will sit next to? No, not really. I do myself no favor,
your best option is to ignore my frustrated sounds and focus on the
technical merits of what I'm saying. If I'm missing something or being
stupid, I invite correction. And at least I'm still here, the other 4D
people of my generation are quiet...because mostly they are gone. Hey, I
like 4D! We all do. I mean, there's no real need to convince 4D people to
use 4D. We all want it to be better.

Since this whole thing has gotten absurdly long, I'll repeat my basic point
on its own:

CALL WORKER is a remote procedure call system that injects EXECUTE(code)
into a process.
If cooperative code is injected into a preemptive process, bad things
happen.
4D should do less bad things and tell us about the problem via ON ERR call.

That's it. It strikes me as a pretty uncontroversial statement so I don't
understand what the fuss is about. Why wouldn't someone thing it makes
sense to provide an error at this point?
> Concept of Workers is very new in V16, you know that you can expect
improvements in the future.

Of course! Discussion of the subject would be pointless if there were no
chance of change. However, I cannot make any plans based on what *might*
happen in the future. So, speculation is of zero practical value for me.

I'll also note that while "workers" are new in 4D V16, the underling
concepts and tools are neither new nor unfamiliar. They're just new in 4D.
Meaning, there are many, many long-standing implementations that 4D very
likely looked at and considered while developing their design. Like any
other programming team, the crew at 4D must have considered alternative
designs when they came up with what is now CALL WORKER and CALL FORM. I can
see why they picked a remote procedure call scheme, but I can't think of a
single other messaging architecture that works that way. But either way, it
was a design choice made in France, not some sort of discovery and not some
sort of law of nature. Their is nothing sacred about the design.

Now, they had to make choices to deliver a product. Their choices have very
good results and less desirable results. I have been continuously praising
the good aspects. So much so that these features convinced me to move my
own development from V13 to V16. I was also excited enough about these
features arriving in 4D to sign up to do my first 4D presentations in a
decade. So, yeah, I'm a fan.

I'm also willing to say what is a weak spot and what I see as preferable
design choices going forward. Error handling has always been a terrible
weak spot in 4D and my latest "feature request" (it's really about a
bug/design flaw) shows me that 4D still doesn't appreciate the importance
of consistent and reliable exception handling.

> You cannot get something at this level of complexity and have all
finished at once, in a perfect way.

And you cannot expect customers not to say that are unsatisfied by an
incomplete implementation. As it stands, the current design makes a great
many normal messaging patterns difficult or impossible to implement. 4D
could have done this sort of design *without more work* and given us a very
different system:

LAUNCH WORKER("Worker_Name";"Worker_Handler_Name"")
CALL WORKER("Worker_Name";$object)
// Worker_Handler_Name (Object)
C_OBJECT($1;$message)
$message:=$1
// Do whatever you like.

That's the simplest alternate version. At that point, the problem I have
been describing *would be impossible to create.* The flaw doesn't come from
some future feature not being implemented, it's a consequence of the design
itself. 4D can improve the situation by trapping the error when running
EXECUTE inside the workerbut the underlying design is what makes it
possible. The positive side of the design is that it's very easy for people
to reuse existing code without having to mess with C_OBJECT. The downside
is that you can blow up your server.

> IMHO, it's the new way (for 4D Developers) to think their application's
programming.
> We go from a synchronous way of programming, into a totally asynchronous
way, from
> loops to messaging (CALL FORM & CALL WORKER), which is not simple for
many developers.

I can't say. Anyone that's dealt with JavaScript has dealt with a vastly
harder to deal with version of asynchronous programming. In order to
achieve many normal results in 4D you'll need to roll your own versions of
features provided by 

Re: Preemptive mode flaw

[David Adams via 4D_Tech]

 > Thanks. Nobody ever mentions that when discussing the feature.

Yes. Has anyone heard if this is an expected feature in a future version?
That would seem like a fair thing.

I'm obviously a lot more into headless and distributed applications than
anything else, so I look at networked 4D systems architecture differently
than some. (But not all.) If I wanted to set up a tolerably stable,
 high-performance 4D Server system, it would look like this:

4D Server
4D Sand-alone merged apps
Some kind of communications layer

In that setup, all of the machines are preemptive capable.

With that said, what I would *really* like to hear are real-world stories
from people getting some advantage out of preemptive mode. And details
about their approach.

Taking a page from Miyako's book, I think that a sensible starting strategy
for a regular 4D Server would be:

* Pick a discrete, time-consuming, CPU-bound task, of course. (Nothing else
could ever be worth the bother.)
* Run the code using Execute on server.

That rules out CALL WORKER, but that's okay. I suspect we're all pretty
careful about what sort of code runs on the server machine!

To communicate with the process on the other CPU, I'd use any number of
old-fashioned tricks. Honestly, I'd be picking jobs that can be described
in either a document or a record. Then the task runner would periodically
poll for new work in either a watch folder or a job table. If we're talking
about large tasks, the polling costs should be low. In fact, if the jobs
are large and rare, just run them on demand in a new process and then let
that process die.

But it would depend on circumstances how best to proceed, of course.
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D Write Pro Interface component

[truegold via 4D_Tech]

Sigh,

> My assumption (unproven as I am looking for the same insight)…

Sorry I’m not sure if this example uses the component or not.

But I did find...

http://blog.4d.com/4d-write-pro-user-interface/

Yes, just create a subform container and then in the Subform properties select 
“WP_Palette” as the detail form.

Then the rest I leave to your discovery.

John…


> Hi,
> 
> I’d take a look at this 4DBlog “ Create your own interface for 4D Write Pro”. 
> There is an example database you can download. My assumption (unproven as I 
> am looking for the same insight) and found this v16 HDI example.
> 
> http://blog.4d.com/create-your-own-interface-for-4d-write-pro/
> 
> And I’m sure then it might make sense of how to use the component.
> 
> Hope that helps,
> John…
> 
>> Can someone point me to instructions on how to use the 4D Write Pro 
>> Interface component.
> 

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D Write Pro Interface component

[truegold via 4D_Tech]

Hi,

I’d take a look at this 4DBlog “ Create your own interface for 4D Write Pro”. 
There is an example database you can download. My assumption (unproven as I am 
looking for the same insight)  and found this v16 HDI example.

http://blog.4d.com/create-your-own-interface-for-4d-write-pro/

And I’m sure then it might make sense of how to use the component.

Hope that helps,
John…

> Can someone point me to instructions on how to use the 4D Write Pro Interface 
> component.

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Counting # of specific characters in string/text

[Alan Chan via 4D_Tech]

Hi Chip,

Thanks for your advice. The discussion is about how optimized Replace String is 
in v16 especially  on * operation even comparing with position(*) which 
supposed to be very fast. It's not about how to design a 4D app with those 
commands.

Alan Chan

4D iNug Technical <4d_tech@lists.4d.com> writes:
>If all we are doing is talking about "how fast is this" then this 
>discussion has no relation to real world usage. 

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D World Tour - Denver

[Floyd Zink via 4D_Tech]

Ditto to what everyone else has already said about the 4D World Tour 2017 in 
Denver. Sorry I’m late posting, but all I can add is the knowledge and advice 
gained from the training is “priceless.” The ROI is off the charts.

All the presenters were well prepared and explained a lot of the new features 
of v16 with excellent demos. Even the “new” guy. ;) Add was great as usual and 
JPR is JPR. :)

It was great seeing several of the old timers and some new, much younger, 
developers as well!

BTW, the term JPR used for the “hypothetical” new version of 4D was it, 
hypothetically, will be a “quantum leap.” Also, you better be all over C_OBJECT.

Floyd Zink
QMed Corporation




**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D Write Pro Interface component

[Ortwin Zillgen via 4D_Tech]

> Can someone point me to instructions on how to use the 4D Write Pro Interface 
> component.

some reading



Regards
O r t w i n  Z i l l g e n
-
   
 
member of developer-network 


**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: POST CLICK on highlight button

[Chip Scheide via 4D_Tech]

I solution might be to check that the button is set to 1 (assuming 
longint)

if (form event = on clicked)
  if (self-> # 1)
self-> := 1
  end if
end if


On Mon, 8 May 2017 17:24:33 +1000, Sujit Shah via 4D_Tech wrote:
> I find a POST CLICK on a highlight button does not put the button in
> highlight. A normal click does.
> 
> I can trap the object event so it definitely does click the button.
> 
> 
> 
> -- 
> 
> xxx
> "There must be ingenuity as well as intention, strategy as well as
> strength. "
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **
---
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing 
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Counting # of specific characters in string/text

[Chip Scheide via 4D_Tech]

The "problem" of using/not using * is knowing whether it is helpful.

If I am looking for all instances of 'e' in the text of a book I can 
NOT use * as e ≠ E ≠ ë etc.
So... either I would need to do repeated loops through the text using 
variations of 'e' (e, E, ë, etc), or I can not use *.

If all we are doing is talking about "how fast is this" then this 
discussion has no relation to real world usage. 

Knowing that it take nearly 20 times as long for position to find a 
character without * is important information, as is knowing that your 
test(s) always used *.

In your example, 4 million characters, 100,000 instances without * 
should be (14 * 20) = ~280ms, assuming that position does not slow down 
even further on multiple instances. While 280 ms is not long, if you 
need to loop over this 100 times it shows to your UI.

14ms * 100 = 1400ms = 1.4 sec  -- user *might* notice
280ms * 100 = 28000 = 28 seconds -- user has powered off the system and 
is restarting thinking the machine froze.  :)

so.. like I said, knowing this is important.



On Sun, 07 May 2017 03:54:22 +0800, Alan Chan via 4D_Tech wrote:
> Hi Chip
> 
> We have been talking about * all along. Without * has never been in my test.
> 
> My test always consider total length of text "and" total count of 
> occurrence. My test is for 4,300,000 length text and 100,000 
> occurrence. It took 14ms on my machine.
> 
> Alan Chan
> 
> 4D iNug Technical <4d_tech@lists.4d.com> writes:
>> v13 testing
>> position - no * find character (u + umlaut) end of 2,000,000 length text
>> 56ms +/- ms
>> 
>> Position (*) - find same character at end of 2,000,000 length text
>> 3 ms +/- 1ms
>> 
>> so... when you know that diacritcallity, or capitalization, is 
>> important Position with * is MUCH faster -- at least in v13
> 
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **
---
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing 
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: 4D World Tour - Denver

[Tom Dillon via 4D_Tech]

Sorry, I failed to mention, but of course, JPR's "poof" was in an eelven on a 
scale of one to ten!

Tom Dillon wrote:

>I know I'm late to this and that there's only the one World Tour event
>left (I had a three day, drinking from a firehose client meeting after
>the WT). BUT, I thought about not going, because, ya know, maybe JPR
>might have lost some of the perk in his "poof, it is done". And I don't
>have enough time to practice how to pronounce Add Komoncharoensiri (I
>have trouble with double letters). But, learning what I did about
>workers and, in particular, a better way of doing modular form design,
>made it more than worth it.
>
>I know, it's tomorrow and I probably can't make most of the first day!
>Do it anyway. You'll thank me, and everyone else who posted about the
>World Tour, probably with a beer at the next 4D Summit.

-- 
   --
   Tom Dillon   825 N. 500 W.
   DataCraft   Moab, UT 84532
   tomdil...@datacraft-inc.com   720/209-6502
   --
   Never apologize for a joke that nobody realized was dirty.
   --- Sunastar
   --


**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: dog's breakfast

[Jim Hays via 4D_Tech]

And regarding "enthusiastic use of language" I haven't seen this referenced
on the NUG - I highly recommend it for anyone that has gotten into
javascript:

https://www.nostarch.com/hemingway



Jim Hays


On Mon, May 8, 2017 at 6:29 AM, David Adams via 4D_Tech <
4d_tech@lists.4d.com> wrote:

> On Mon, May 8, 2017 at 8:22 PM, Benedict, Tom via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
>
> >
> > "It was enough of a dog's breakfast..."
> >
>
> I first heard it from the lips of Keith Goebel about 15 years ago. Such a
> great phrase. Sure, he's a Kiwi, but we don't hold that against him ;-)
>
>  In America, I much enjoy the phrase "dumpster fire", which seems to have
> become a commonly-used adjective in the past year.
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **
>
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Preemptive mode flaw

[Jeffrey Kain via 4D_Tech]

Thanks. Nobody ever mentions that when discussing the feature.

> On May 8, 2017, at 8:49 AM, Epperlein, Lutz (agendo) 
>  wrote:
> 
> http://doc.4d.com/4Dv16R2/4D/16-R2.1620/Preemptive-4D-processes.300-3111846.en.html
> 
> look at "Availability of preemptive mode"
> 
> The use of preemptive mode is available in 4D 64-bit versions only. The 
> following execution contexts are currently supported:
> Preemptive execution
> 4D Server X
> 4D remote -
> 4D single-userX
> Compiled mode X
> Interpreted mode  -

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

RE: Preemptive mode flaw

[Epperlein, Lutz (agendo) via 4D_Tech]

http://doc.4d.com/4Dv16R2/4D/16-R2.1620/Preemptive-4D-processes.300-3111846.en.html

look at "Availability of preemptive mode"

The use of preemptive mode is available in 4D 64-bit versions only. The 
following execution contexts are currently supported:
Preemptive execution
4D Server   X
4D remote   -
4D single-user  X
Compiled mode   X
Interpreted mode-



> -Original Message-
> From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Jeffrey Kain 
> via
> 4D_Tech
> Sent: Monday, May 8, 2017 2:47 PM
> To: 4D iNug Technical <4d_tech@lists.4d.com>
> Cc: Jeffrey Kain 
> Subject: Re: Preemptive mode flaw
> 
> Is it still the case that client/server applications are excluded from 
> running preemptive
> 4D code?
> 
> --
> Jeffrey Kain
> jeffrey.k...@gmail.com
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Preemptive mode flaw

[Jeffrey Kain via 4D_Tech]

Is it still the case that client/server applications are excluded from running 
preemptive 4D code?

--
Jeffrey Kain
jeffrey.k...@gmail.com

> On May 7, 2017, at 9:03 PM, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> then there is the second, runtime (or platform) check.
> unicode mode must be active, the app must be 64-bit, compiled, the type must 
> be either server or desktop.
> if none of these conditions are met, all processes are automatically 
> cooperative, no error.

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: dog's breakfast

[David Adams via 4D_Tech]

On Mon, May 8, 2017 at 8:22 PM, Benedict, Tom via 4D_Tech <
4d_tech@lists.4d.com> wrote:

>
> "It was enough of a dog's breakfast..."
>

I first heard it from the lips of Keith Goebel about 15 years ago. Such a
great phrase. Sure, he's a Kiwi, but we don't hold that against him ;-)

 In America, I much enjoy the phrase "dumpster fire", which seems to have
become a commonly-used adjective in the past year.
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: dog's breakfast

[Benedict, Tom via 4D_Tech]

David Adams included this gem in a recent post:

"It was enough of a dog's breakfast..."

That's a phrase we don't hear enough of on this side of the pond.

Thank you, David, for your enthusiastic use of language, programming or 
otherwise. It's always a pleasure to read your posts, whether or not I have a 
technical interest in them.

Tom Benedict
Optum
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Bar code

[stardata.info via 4D_Tech]

I try this:
$0:=ZINT 
($1;ZINT_Format_PNG;BARCODE_CODE128;$optionNames;$optionValues;$textData)


But i not have any image

Thanks
Ferdinando

Il 08/05/2017 11:16, Spencer Hinsdale ha scritto:

Try PNG. I think scaling does not work with SVG because of crisp edges.

-Spencer


On May 8, 2017, at 1:57 AM, stardata.info via 4D_Tech <4d_tech@lists.4d.com> 
wrote:

Hello,

I try to use Picture:=Picture*,09 but not work because some part of bar code 
are differents

Thanks
Ferdinando





**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Bar code

[Spencer Hinsdale via 4D_Tech]

Try PNG. I think scaling does not work with SVG because of crisp edges.

-Spencer

> On May 8, 2017, at 1:57 AM, stardata.info via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> Hello,
> 
> I try to use Picture:=Picture*,09 but not work because some part of bar code 
> are differents
> 
> Thanks
> Ferdinando
> 
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Bar code

[stardata.info via 4D_Tech]

Hello,

I try to use Picture:=Picture*,09 but not work because some part of bar 
code are differents


Thanks
Ferdinando

Il 08/05/2017 09:24, 4d_tech-requ...@lists.4d.com ha scritto:

Message: 5
Date: Mon, 8 May 2017 01:57:35 +
From: Keisuke Miyako
To: 4D iNug Technical<4d_tech@lists.4d.com>
Subject: Re: Bar code
Message-ID:
Content-Type: text/plain; charset="utf-8"

Hello,

the plugin returns a regular picture (you have the choice between PNG and SVG) 
so you should be able to use regular picture commands,
such as PICTURE PROPERTIES, TRANSFORM PICTURE, or even picture operators.

http://doc.4d.com/4Dv16R2/4D/16-R2.1620/PICTURE-PROPERTIES.301-3111814.en.html
http://doc.4d.com/4Dv16R2/4D/16-R2.1620/TRANSFORM-PICTURE.301-3111801.en.html
http://doc.4d.com/4Dv16R2/4D/16-R2.1620/Picture-Operators.300-3111968.en.html


2017/05/08 2:53、stardata.info via 4D_Tech<4d_tech@lists.4d.com>  のメール：
Work well but i need to reduce the dimension of bar code that i obtain, because 
i have few space in my label


**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

4D Write Pro Interface component

[John Baughman via 4D_Tech]

Can someone point me to instructions on how to use the 4D Write Pro Interface 
component.

Thanks,

John
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

POST CLICK on highlight button

[Sujit Shah via 4D_Tech]

I find a POST CLICK on a highlight button does not put the button in
highlight. A normal click does.

I can trap the object event so it definitely does click the button.



-- 

xxx
"There must be ingenuity as well as intention, strategy as well as
strength. "
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**