Thanks Jody,
I gave it 4 stars … like everyone else did.
— Chris
> On Jun 24, 2019, at 4:19 PM, Jody Bevan via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Chris Belanger:
>
> To vote, to to the top of the first post. There are 4 yellow starts. Click on
> the first star to indicate - ya it
Kirk,
The label files were created with the 4D v17.2 64-bit label editor.
--
Jeff Grann
SuccessWare, Inc.
> On Jun 24, 2019, at 8:39 PM, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Jeff,
> Sorry, I didn't read your original email closely enough.
> I just updated the
it depends on the device.
if it is an Human Interface Devices,
https://docs.microsoft.com/en-us/windows-hardware/drivers/hid/introduction-to-hid-concepts
https://developer.apple.com/documentation/kernel/iohiddevice?language=objc
you normally interact via an installed device driver.
if not
Jeff,
Sorry, I didn't read your original email closely enough.
I just updated the code I posted to:
$DocType:="com.adobe.pdf;com.4d.4d.labelFile;.jpeg;.txt;.text;.csv;.json"
I was able to select both a PDF and a label file I just created. Perhaps
there is some sort of permission block? Or, how
the documentation gives examples of public UTIs.
https://doc.4d.com/4Dv17R5/4D/17-R5/Select-document.301-4127312.en.html
https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/understanding_utis/understand_utis_conc/understand_utis_conc.html
it seems like public UTIs
Hi Kirk.
The docs say to place semicolons between file types. The issue seems to be
they also say to use UTIs on Mac, which don’t seem to work. Only extensions
work.
--
Jeff Grann
SuccessWare, Inc.
> On Jun 24, 2019, at 8:03 PM, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com>
>
Jeff,
I have only had luck using Select document when the file types are separate
by semi colons. Here's an example from working code:
*C_TEXT*($doc;$DocType)
*ARRAY TEXT*($aDocs;0)
$DocType:=".pdf;.jpg;.jpeg;.txt;.text;.csv;.json"
$Doc:=*Select document*(*System
David,
Hi. I believe your starting point will be the "Communication" section of the
docs. For the latest v17.3 this is the link:
https://doc.4d.com/4Dv17/4D/17.2/Communications.201-4385988.en.html
HTH.
Regards,
Narinder Chandi,
ToolBox Systems Ltd.
--
-Original Message-
From:
I am wanting to do 2-way communication with a USB device directly from
within 4D. I need to send command codes to the device and then receive
data back from the device.
Does anyone have experience with this? Ideally, some help in finding some
technical documentation on how to do this would be
Chris Belanger:
To vote, to to the top of the first post. There are 4 yellow starts. Click on
the first star to indicate - ya it would be nice, Click on the 4th star to
indicate it is a very very good idea. The 2nd and 3rd stars are in between
those thought levels.
The little number to the
Just tested the link for ‘examples’ and it only brought up my default Forum
page.
How do I navigate to the ’samples’ page?
Thanks,
Chris
> On Jun 21, 2019, at 11:11 AM, John DeSoi via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> This was just discussed and requested on the Forums. Some
Thanks, John.
All I did to ‘vote’ for it was to reply “Me Too”. Is there a more ‘official’
way to upvote a feature request?
— Chris
> On Jun 21, 2019, at 11:11 AM, John DeSoi via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> This was just discussed and requested on the Forums. Some examples were
Hi Tom,
I am facing the same challenge.
I am afraid there is no cross-reference documentation at this moment. I am
planning on going through the classic 4D Write code line by line and see what
needs to be done.
It’s not only the code: there is also the paradigm shift to object oriented…
only
I would try passing the extension (.4lbp)
On Mon, 24 Jun 2019 15:01:34 -0400, jeff--- via 4D_Tech wrote:
> In 4D v17.2 on MacOS 10.14.3, I am attempting to open a 64-bit label
> format file using Select document. I am passing "com.4d.4d.labelFile"
> in the fileTypes parameter but all such files
I’ve started a project to convert a large library of 4D Write Classic code to
4D Write Pro.
I’ve read the various tech notes and blogs about 4DWrite Pro, along with the
official 4D documentation, but I have a very hard time keeping track of it all.
Some commands are now in the Styled Text
If you are putting this into a Terminal script, then I always just use the
MacOS Copy Pathname from the right click on the file name (then press the
option key). When the MacOS places the pathname into the pasteboard it will
have the appropriate syntax (escaping out the spaces) as needed for
Jermey,
follows code that should resolve your conversion to posix
//fileutl_Path_Convert_to_Posix
//$1 - Text - Path to convert
//Original from JorgeChB via iNug
//Converts a Mac file path to a Posix form
//RETURNS - Text - converted path, or empty string if path is empty,
or error
Hi Jeremy,
Two options:
- surround your path with single quotes. If the path itself includes quotes,
you will need to escape them.
'/Users/jeremyfrench/Desktop/test_notarize_01/test_notarize_01_Build/Final
Application/test_notarize_01.app/'
- escape the spaces:
How do we resolve POSIX file path syntax between 4D and Mac Terminal?
This Mac system path has a space in the folder name "Final Application":
Macintosh
HD:Users:jeremyfrench:Desktop:test_notarize_01:test_notarize_01_Build:Final
Application:test_notarize_01.app:
4D's POSIX shows the space in
19 matches
Mail list logo
